Add bump_major support for chart version bumps when webhook minor version increases #1193
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.
Issue:
Port of rancher/turtles@7884d64
Problem
When releasing a new webhook minor version (e.g., v0.5.0 → v0.6.0-rc.0), the chart major version needs to be bumped (e.g., 104.0.0 → 105.0.0). The existing release scripts only support patch version bumps.
Solution
Added
bump_majorparameter to release workflows and scripts:.github/workflows/release-charts.yaml/release-rancher.yaml: Addedbump_majorworkflow input (choice:true/false).github/workflows/scripts/release-against-charts.sh/release-against-rancher.sh:bump_major()function (increments major, resets minor/patch to 0)cut -d. -f2for simplified extractionbump_majoris now a required argument (must be "true" or "false")bump_major=trueUsage examples from updated script help:
CheckList
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.