Repository navigation
fix: add always-bump-minor versioning to prevent automated major bumps - #113
Jacob (JacobPEvans-personal) wants to merge 1 commit into
Conversation
Adds "versioning": "always-bump-minor" to release-please config, which prevents release-please from ever computing a major version bump regardless of BREAKING CHANGE footers. Major bumps are human-initiated only via .release-please-manifest.json. (claude)
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request implements a crucial change to the Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on Gemini (@gemini-code-assist) comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request modifies release-please-config.json to set the versioning strategy to always-bump-minor, which will prevent release-please from automatically creating major version bumps. A comment has also been added to document this as an organizational policy. The change is correct and effectively implements the desired versioning behavior. I have no further feedback.
There was a problem hiding this comment.
Pull request overview
Updates the repository’s release-please configuration to enforce an org-wide “no automated major bumps” policy, aligning automated releases with the intended versioning approach.
Changes:
- Adds
versioning: "always-bump-minor"to prevent release-please from automatically computing major version bumps. - Adds a
$commententry documenting the policy to reduce the chance of accidental removal later.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
Superseded by centralized enforcement in JacobPEvans/.github#123 — the shared workflow now injects |
Summary
"versioning": "always-bump-minor"torelease-please-config.json— a native release-please setting that prevents automated major version bumps$commentdocumenting the org-wide policy so the key doesn't get silently removed againTest plan
🤖 Generated with Claude Code