Repository navigation
ci(nav3): [Part 12] Keep compatibility coverage current - #6709
0xadam-brown wants to merge 1 commit into
Conversation
PR risk: mediumFor commit The model rated this change low. It was raised to medium because:
This label is a hint for reviewers, not an approval. |
📲 Install BuildsAndroid
|
5ddd798 to
7d85cf6
Compare
a3da611 to
08d30db
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 08d30db. Configure here.
| name: Nav3 kotlinx.serialization R8 check | ||
| # Only the R8 verification app uses this version; the SDK's dependency doesn't change. | ||
| changelog-entry: false | ||
| ssh-key: ${{ secrets.CI_DEPLOY_KEY }} |
There was a problem hiding this comment.
Prerelease tags can stall version updates
Medium Severity
The nav3 updater omits pattern, so kotlinx.serialization RC tags are treated as latest. get-version and set-version only match [0-9.]+ before a quote, so once defaultLatestKotlinx is an RC those commands stop matching and the pin cannot move to the later stable tag.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit 08d30db. Configure here.


PR Stack (Nav3 Serial Name Mappers)
📜 Description
Keeps Nav3’s R8 compatibility tests current by checking for kotlinx.serialization releases weekly and proposing updates to the newer runtime tested alongside the supported floor.
💡 Motivation and Context
The properties mapper uses serialization’s experimental encoding API, and host apps determine which runtime it runs against. Exercising newer releases in R8-minified apps helps catch API and shrinker-rule incompatibilities before the next SDK release, without raising the SDK’s minimum supported version.
addresses: JAVA-787 (link)
💚 How did you test it?
n/a
📝 Checklist
sendDefaultPIIis enabled.🔮 Next steps
Once the numbered slices have been reviewed and merged into the collection branch, review the aggregate change and squash-merge the collection PR into
main.#skip-changelog