Skip to content

ci(nav3): [Part 12] Keep compatibility coverage current - #6709

Draft
0xadam-brown wants to merge 1 commit into
feat/nav3-serial-name-mappers-11from
feat/nav3-serial-name-mappers-12
Draft

0xadam-brown wants to merge 1 commit into
feat/nav3-serial-name-mappers-11from
feat/nav3-serial-name-mappers-12

Conversation

@0xadam-brown

@0xadam-brown 0xadam-brown commented Nov 20, 2026 •

Copy link
Copy Markdown
Member

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

  • I added GH Issue ID & Linear ID
  • I added tests to verify the changes.
  • No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
  • I updated the docs if needed.
  • I updated the wizard if needed.
  • Review from the native team if needed.
  • No breaking change or entry added to the changelog.
  • No breaking change for hybrid SDKs or communicated to hybrid SDKs.
  • Public API changes reviewed by another Mobile SDK team member or implemented according to the develop docs spec.

🔮 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.

⚠️ Merge this PR using a merge commit (not squash). Only the collection branch is squash-merged into main.

#skip-changelog

@github-actions

github-actions Bot commented Nov 20, 2026 •

Copy link
Copy Markdown
Contributor

PR risk: medium

For commit 08d30db.

The model rated this change low. It was raised to medium because:

  • R6: build or release configuration changed: .github/workflows/update-deps.yml, scripts/update-nav3-kotlinx-serialization.sh
  • R7: the model was not confident enough that the change is low

This label is a hint for reviewers, not an approval.

@github-actions github-actions Bot added risk: medium PR risk score: medium and removed risk: medium PR risk score: medium labels Nov 20, 2026
@sentry

sentry Bot commented Nov 20, 2026 •

Copy link
Copy Markdown

📲 Install Builds

Android

🔗 App Name App ID Version Configuration
SDK Size io.sentry.tests.size 8.65.0 (1) release

⚙️ sentry-android Build Distribution Settings

@0xadam-brown
0xadam-brown force-pushed the feat/nav3-serial-name-mappers-11 branch from 5ddd798 to 7d85cf6 Compare November 20, 2026 14:00
@0xadam-brown
0xadam-brown force-pushed the feat/nav3-serial-name-mappers-12 branch from a3da611 to 08d30db Compare November 20, 2026 14:00
@github-actions github-actions Bot added risk: medium PR risk score: medium and removed risk: medium PR risk score: medium labels Nov 20, 2026
@0xadam-brown 0xadam-brown changed the title ci(nav3): [Nav3 Mappers 12] Keep compatibility coverage current ci(nav3): [Part 12] Keep compatibility coverage current Nov 20, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

risk: medium PR risk score: medium

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant