Skip to content

feat: drop the pre-release label from a promoted release's names - #9

Merged
ThePhaseless merged 1 commit into
mainfrom
feat/rename-promoted-release
Oct 6, 2026
Merged

ThePhaseless merged 1 commit into
mainfrom
feat/rename-promoted-release

Conversation

@ThePhaseless

Copy link
Copy Markdown
Contributor

Promoting a pre-release (unticking "Set as a pre-release") kept its beta names on GitHub, e.g. Plan WZIM's 4.3.0 showed as "Plan WZIM 4.3.0 beta 4" with plan-wzim-v4.3.0-beta.4.aab. The stores already used 4.3.0.

  • New rename job after the promotion check: the title loses the label (App 1.2.0 beta 3 → App 1.2.0, v1.2.0-beta.3 → v1.2.0, an empty title becomes v1.2.0), and the build files are renamed after the release. Titles that don't contain the version with that label and number are left alone. The tag keeps the label.
  • The promotion check accepts the renamed files, so a re-run still works.
  • Pages waits for the rename.

mise run lint:actions, lint:markdown and test pass; the title/file logic was tested on sample names.

🤖 Generated with Claude Code

Unticking "pre-release" left the GitHub release titled "App 1.2.0 beta 3"
with beta build files. The promotion now renames the title and the files;
the tag keeps the label.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ThePhaseless
ThePhaseless merged commit 790bab8 into main Oct 6, 2026
2 checks passed
@ThePhaseless
ThePhaseless deleted the feat/rename-promoted-release branch October 6, 2026 13:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant