release: prepare v1.5.2 (versionName 1.5.2, new release notes) - #14
Merged
Merged
Conversation
The v1.5.1 release workflow failed before publishing and Play already serves 1.5.1 as versionCode 10, so the build that carries per-model detection (#10) ships as v1.5.2 and the existing v1.5.1 tag is left alone. - app and glass-hud: versionName 1.5.1 -> 1.5.2 (versionCode stays 11 / 8) - doc/RELEASE_NOTES_v1.5.2.md: new, bilingual, covers 1.5.0 through 1.5.2 since this is the first GitHub Release since v1.4.0 - doc/RELEASE_NOTES_v1.5.1.md: restored to what Play's 1.5.1 (versionCode 10) shipped, undoing the versionCode 11 edits from the earlier bump Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
|
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.



Why
The
v1.5.1Release run failed before publishing (fixed in #13), and Play already serves 1.5.1 as versionCode 10. Rather than move thev1.5.1tag, the build that carries #10 ships as v1.5.2, and the existingv1.5.1tag is left untouched.Changes
app,glass-hud:versionName1.5.1 -> 1.5.2.versionCodestays 11 / 8; neither has been published anywhere.doc/RELEASE_NOTES_v1.5.2.md(new, bilingual). The release workflow publishesdoc/RELEASE_NOTES_<tag>.md, so this is the GitHub Release body. It covers 1.5.0 through 1.5.2, since this is the first GitHub Release since v1.4.0, and includes the Play "What's new" text.doc/RELEASE_NOTES_v1.5.1.md: restored to the content at8b91f73, i.e. what Play's 1.5.1 (versionCode 10 / 7) actually shipped. release: bump to versionCode 11 / 8 for the next Play upload #12 had edited it for versionCode 11, which no longer applies.No source change beyond the two version strings.
Notes on the release notes
Before tagging
v1.5.2mainand push only that tag🤖 Generated with Claude Code