Repository navigation
ci: forward the version bump to ktsubuild release - #35
Merged
Merged
Conversation
The pipeline step already receives --version-bump. The release step now receives the same value, so a forced bump over commits that all carry [skip ci] releases the version the pipeline step committed instead of being skipped.
|
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.
Summary
The Release step in the shared
dotnet.ymlnow passes the dispatch'sversion-bumptoktsubuild release, the same way the KtsuBuild pipeline step already passes it toktsubuild ci.Without it, a forced bump over commits that all carry
[skip ci]gets stuck between the two steps. The pipeline step commits the forced version to VERSION.md, and the Release step then resolvesautoand skips. That happened on 2026-10-14 with patch dispatches on GitBranchStateCache and GitLfsCache.The input reaches the script through an environment variable rather than inline expansion. That's because the input is typed
string, so a caller can put anything in it.Merge order
Keep this as a draft until ktsu-dev/KtsuBuild#246 is released. That PR adds
--version-bumptoktsubuild release. The workflow installs the latestktsu.KtsuBuild.Tool, and an older one rejects the unknown option, which would fail every forced-bump release.Runs with
auto, including every push and scheduled run, don't pass the option. They're unaffected whatever the merge order.Test plan
release, apatchdispatch on a repo whose only new commits are[skip ci]creates the release and the container image🤖 Generated with Claude Code