-
-
Notifications
You must be signed in to change notification settings - Fork 0
fix: Disable automated major version bumps in CI #543
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -3,10 +3,9 @@ name: Auto Versioning and Release | |||||
| # SEMANTIC VERSIONING RULES: | ||||||
| # - PATCH (0.14.1 → 0.14.2): fix:, perf:, refactor:, docs:, style:, test:, build:, ci: | ||||||
| # - MINOR (0.14.1 → 0.15.0): feat:, feat(...): | ||||||
| # - MAJOR (0.14.1 → 1.0.0): feat!:, fix!:, or "BREAKING CHANGE: <description>" (NOT "BREAKING CHANGE: None") | ||||||
| # - MAJOR (0.14.1 → 1.0.0): MANUAL ONLY - Create git tag manually when ready for 1.0.0 | ||||||
| # | ||||||
| # ⚠️ IMPORTANT: Do NOT use "BREAKING CHANGE: None" in commit messages - it triggers a major bump! | ||||||
| # Instead, omit the BREAKING CHANGE line entirely if there are no breaking changes. | ||||||
| # ⚠️ Major version bumps are intentionally disabled in automation to prevent accidents. | ||||||
|
|
||||||
| on: | ||||||
| push: | ||||||
|
|
@@ -34,16 +33,13 @@ jobs: | |||||
| with: | ||||||
| # The prefix to use to create tags | ||||||
| tag_prefix: "v" | ||||||
| # Regex pattern for major version bump (breaking changes) | ||||||
| # Matches ONLY actual breaking changes, not "BREAKING CHANGE: None" | ||||||
| # Pattern: !: in commit type OR "BREAKING CHANGE:" followed by non-None text | ||||||
| major_pattern: "/(feat|fix|chore|refactor|perf|test|docs|style|build|ci)!:|BREAKING CHANGE:(?!\\s*None)/" | ||||||
| # Regex pattern for major version bump - DISABLED (manual only) | ||||||
| # Use a pattern that will never match to prevent automated major bumps | ||||||
| major_pattern: "/__MANUAL_MAJOR_BUMP_ONLY__/" | ||||||
| # Regex pattern for minor version bump (new features) | ||||||
| # Matches: "feat:" prefix in commit messages (Conventional Commits) | ||||||
| minor_pattern: "/(feat|feat\\()/" | ||||||
|
||||||
| minor_pattern: "/(feat|feat\\()/" | |
| minor_pattern: "/feat(\\(|:)/" |
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The pattern uses double underscores which, while functional as an unmatchable pattern, is not a standard regex practice. A more conventional approach would be to use a pattern that explicitly cannot match any valid commit message, such as
"^(?!.*).*$"(matches nothing) or simply an empty string""if the action supports it. However, the current pattern is clear in intent and will work correctly, so this is a style preference rather than a functional issue.