chore(release): key the Play notes to 1.1.1 (10101) - #161
Merged
Conversation
1.1.0 never shipped; the release went out as 1.1.1 but the Play notes were keyed 10100, so the metadata gate blocked the upload again. Key them 10101 and retitle the CHANGELOG section. The GitHub Releases failure in the same run was a GitHub outage, not a repo problem.
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.
The 1.1.1 tag run (32050347830) confirmed the cosign 2.6.5 fix: harden and SLSA provenance are green. Two jobs still failed, only one of them ours:
changelogs/10101.txt(tag 1.1.1 derives versionCode 10101), but fix(release): unblock the 1.1.0 release (Play 10100 notes + cosign 2.6.5) #160 keyed the notes as 10100 for the abandoned 1.1.0 tag. This PR renames them in all 5 locales (content unchanged) and retitles the CHANGELOG section to 1.1.1. Validated locally:EXPECTED_VERSION_CODE=10101 python scripts/check_play_metadata.pyreports 0 errors.No server is currently available to service your requestis the ongoing GitHub outage, not a repo problem. No change needed; the rerun after re-tagging covers it.Re-releasing after merge (once GitHub recovers)
Nothing shipped from the failed 1.1.1 run (no Play upload, no GitHub release), so moving the tag is clean. If you would rather cut 1.1.2 instead, rename the five files to 10102.txt first; the gate keys on the exact tag-derived versionCode. The stray 1.1.0 tag still points at the broken snapshot and can be deleted.