Skip to content

docs: changelog for 0.6.0 - #104

Merged
jamesarich merged 1 commit into
mainfrom
release/0.6.0
Jul 26, 2026
Merged

docs: changelog for 0.6.0#104
jamesarich merged 1 commit into
mainfrom
release/0.6.0

Conversation

@jamesarich

Copy link
Copy Markdown
Collaborator

Prepares the 0.6.0 release notes. mqtt's [Unreleased] section was empty even though a public-API feature had merged, so this documents everything since v0.5.0.

Headline: the TLS trust hook on TcpTransportFactory (#103) — new public API, hence a minor bump rather than a patch. It is additive and both source- and binary-compatible (the no-arg constructor is retained), so existing call sites are unaffected.

Also covered: the explicitApi() + JVM/klib ABI lock (#87), transport-ws test coverage (#94), AGP 9.3.1 / Kover 0.9.9, and the CI SHA-pinning + Scorecard hardening (#89, #96). Kotlin stays 2.4.10, so native/iOS consumers need no toolchain change from 0.5.0.

Deliberately excluded: the org.meshtastic:protobufs bump (#88) is sample-only and ships in no published artifact.

Once this merges, cutting the release is git tag v0.6.0 && git push origin v0.6.0release.yml derives the version from the tag.

Documents the release: the TLS trust hook (#103) as the headline addition, the explicitApi/klib ABI lock (#87), transport-ws test coverage (#94), AGP/Kover bumps, and the CI SHA-pinning/Scorecard hardening. Notes that Kotlin stays 2.4.10, so klib consumers need no toolchain change from 0.5.0.

Minor rather than patch: #103 adds public API (a new optional TcpTransportFactory constructor parameter). The change is source- and binary-compatible — the no-arg constructor is retained.
Copilot AI review requested due to automatic review settings July 26, 2026 17:54
@jamesarich
jamesarich enabled auto-merge July 26, 2026 17:54
@coderabbitai

coderabbitai Bot commented Jul 26, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@jamesarich, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 5 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: f5ca5495-3438-4b0b-8d5c-33dff057eb21

📥 Commits

Reviewing files that changed from the base of the PR and between 1a9ad6a and 2a04eb6.

📒 Files selected for processing (1)
  • CHANGELOG.md

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@jamesarich
jamesarich disabled auto-merge July 26, 2026 17:54
@jamesarich
jamesarich merged commit 72f350d into main Jul 26, 2026
13 checks passed
@jamesarich
jamesarich deleted the release/0.6.0 branch July 26, 2026 17:54

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Prepares the v0.6.0 release notes by filling in the previously empty [Unreleased] section, documenting the user-visible API addition (TLS trust hook for TcpTransportFactory) plus related build, test, and CI/security hardening work since v0.5.0.

Changes:

  • Added a 0.6.0 changelog entry highlighting the new TcpTransportFactory TLS trust customization hook and its compatibility/ordering notes.
  • Documented build/public-API hardening (explicitApi() + JVM/klib ABI baselines), added transport-ws test coverage, and updated tooling versions.
  • Noted CI security posture improvements (SHA-pinned Actions + OpenSSF Scorecard).

Comment thread CHANGELOG.md
Comment on lines +26 to +28
link unchanged. On Android this replaces the previous workaround of opting the entire
app into user-installed CAs via `network_security_config.xml`, which affected every
HTTPS connection the app made. See `transport-tcp/Module.md` for the trust-ordering
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants