feat(release): cut a release on every merge to main#6
Merged
xergioalex merged 1 commit intomainfrom May 2, 2026
Merged
Conversation
…efix ## Summary Drops the requirement that contributors remember `feat:`/`fix:`/etc. prefixes for a release to happen. From now on, every merge to main ships at least a PATCH release; the conventional-commit prefixes are optional and only matter for choosing between PATCH / MINOR / MAJOR. This matches a continuous-deployment philosophy: every change that reaches `main` is, by definition, a change worth shipping. Lowers the cognitive load on contributors and removes a class of "I merged but nothing got released — why?" support questions. Trade-off: more releases (small typo fixes also bump the version). That is intentional — the version number is treated as a counter of "changes shipped to users", not a curated narrative of major events. ## Change Log - `pyproject.toml::[tool.semantic_release.commit_parser_options]`: `default_bump_level` flipped from `0` (no release if no qualifying commits) to `1` (any commit triggers PATCH). Inline comment now enumerates the new behavior table for future maintainers. - `AGENTS.md` Rule 15 (Packaging & Versioning): rewrote the bullet about the default release path to reflect the unconditional-release policy. Conventional-commit prefixes still unlock finer control, they are no longer required. ## Risks - More frequent PyPI releases. Each one is small (one PR's worth of changes), so this is not a meaningful infra cost. PyPI does not rate-limit at this volume. - The version number escalates faster. We are now on 1.0.x; with this policy each merge yields 1.0.x+1 or higher. Acceptable trade-off for the simpler contributor experience. ## How this is verified - `codecheck` (lint + format + mypy + 128 tests) green. - `semantic-release --noop version --print` parses the new config without error. - After this PR is merged, the next merge of any kind (even a typo fix or a docs-only change) will cut a release. We will see this in practice immediately. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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
Switches the release model so every merge to
mainships at least a PATCH release, regardless of whether the commits follow conventional-commit prefixes. Lowers the cognitive load on contributors — no more "I merged but nothing got released" surprise.What changes
pyproject.toml::[tool.semantic_release.commit_parser_options]:default_bump_levelfrom0→1Behavior matrix:
feat:1.0.1 → 1.1.0)fix:/perf:1.0.1 → 1.0.2)feat!:orBREAKING CHANGE:bodychore:/docs:/refactor:/ no prefix at allConventional-commit prefixes are still honored — they let you upgrade from PATCH to MINOR/MAJOR. They are just no longer required.
AGENTS.mdRule 15 was rewritten to reflect the new policy.Trade-off
More frequent PyPI releases. Each one is small. Acceptable for the simpler contributor experience.
How this validates
After this PR is merged, the very next PR (any PR) will cut a release. We will see it work immediately in practice.
Test plan
codecheck(ruff + format + mypy + 128 tests) green locallysemantic-release --noop version --printparses the new config without error