Manual Release Pipeline #17
Merged
Conversation
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
- Build results uploaded under packages, the reason for that is during development we might want to test intermediate builds in some systems(usually in some other systems which consumes storage-cli and uses)and see that our new developed feature worked out. When developments are done we can create PR and once PR goes into main new release will be created.
cf-foundation-community-automation
bot
moved this to Inbox
in Foundational Infrastructure Working Group
stephanme
approved these changes
Dec 17, 2025
github-project-automation
bot
moved this from Inbox
to Pending Merge | Prioritized
in Foundational Infrastructure Working Group
github-project-automation
bot
moved this from Pending Merge | Prioritized
to Done
in Foundational Infrastructure Working Group
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Context
The repository is under active development, and using an automatic release pipeline would result in frequent and unnecessary releases.
Solution
A manual release pipeline has been introduced. Releases can now be created either via workflow dispatch or from the GitHub Releases page using a draft release. To create a new release, the version must start with the v prefix and follow the next incremented version number.