Repository navigation
ci(nav3): [Part 12] Keep compatibility coverage current - #6709
Draft
0xadam-brown wants to merge 1 commit into
Draft
0xadam-brown wants to merge 1 commit into
0xadam-brown wants to merge 1 commit into
Conversation
This was referenced Nov 20, 2026
Contributor
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
|
0xadam-brown
force-pushed
the
feat/nav3-serial-name-mappers-11
branch
from
November 20, 2026 14:00
5ddd798 to
7d85cf6
Compare
0xadam-brown
force-pushed
the
feat/nav3-serial-name-mappers-12
branch
from
November 20, 2026 14:00
a3da611 to
08d30db
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR Stack (Nav3 Serial Name Mappers)
📜 Description
A weekly update keeps the newer serialization version used for verification current while leaving the SDK’s compilation floor fixed. That makes upstream API and shrinker-rule changes visible without silently raising the minimum serialization version supported by the SDK.
💡 Motivation and Context
Compatibility checks cannot reveal problems in a new serialization release until that release is tested.
addresses: JAVA-787 (link)
💚 How did you test it?
Verified the updater’s version read/write protocol and a version round-trip, including that the compilation floor remained unchanged. Both workflow YAML files and shell scripts passed syntax checks. All 872 Nav3 unit tests and the sample build passed; the SDK and R8 fixture code are unchanged from the preceding validated slice.
📝 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