Repository navigation
Coordinate client and server release versions - #8
Merged
Merged
Conversation
This was referenced Oct 4, 2026
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Add a coordinated
1.0.0release snapshot for client/server with Android build number 1.tools/release.py bumpupdates both component manifests and the server's own lock entry without upgrading dependencies;check --committedvalidates the component gitlinks recorded in the workspace rather than dirty working copies.Add focused release CI and a runbook covering independent component merge order, server-first rollout, signing/endpoint settings and first Google Play internal testing. Record the companion client/server preparation commits. The client reader pin now agrees with the existing workspace reader; the two previously mismatched reader revisions have identical source trees.
Validation: five coordinated-version regressions, local and committed release checks, workspace reader reference checks, workflow actionlint and existing tooling checks. Component validation includes an actual signed test AAB/16 KB checks and a disposable PostgreSQL/PowerSync deployment smoke test. Public deployment, Play Console setup, real upload credentials and device testing are not performed.
Merge the companion client/server PRs first and refresh these gitlinks if their merge strategy changes commit IDs. Configure the client
releaseenvironment and public server before manually dispatching the initial client build; preparation alone does not publish to Play.Companion PRs: PapyrusReader/client#33 and PapyrusReader/server#8.