Repository navigation
ci(release): add skip_bump to record a production release without a patch bump - #1674
Merged
Merged
Conversation
…atch bump The workflow bumps Flipcash.patchVersion whenever production changes. When Packaging.kt is already ahead of the release being recorded (Play promoted 2026.9.4 while code/cash was on 2026.10.1), the only way to update the manifest was to run the script locally. skip_bump writes the manifest and stops before the bump; the commit reads "build: release Flipcash <name> (<code>)". Setting it with force_bump fails. emit() also no longer ends on a failing `[ -n "$GITHUB_OUTPUT" ]` test, which under set -e stopped local runs after the first output.
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
1 participant
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 bump-patch workflow bumps
Flipcash.patchVersionwhenever production changes. Play promoted 2026.9.4 (4676) to production whilecode/cashwas already on 2026.10.1, so recording it meant runningupdate-release-manifest.shlocally to avoid a bump to 2026.10.2 (eed474877).skip_bumpinput (SKIP_BUMPin the script): writes the manifest, emitsskipped=true, and exits before touchingPackaging.kt. The commit message isbuild: release Flipcash <name> (<code>).force_bumpandskip_bumptogether exit 1.emit()used[ -n "$GITHUB_OUTPUT" ] && …as its last line; withset -eand noGITHUB_OUTPUT, local runs stopped after the first output. It's anifnow.