chore: release 0.1.0 - #15
Merged
Merged
Conversation
The bump refused to run when pyproject.toml already carried the requested version, which is exactly the state of a first release. It now validates everything before writing anything, treats an already-set version as a no-op substitution, and refuses only when the changelog already has a section for that version or has nothing to release. Tests cover the first release, the refusal after a cut, and that a refused bump writes nothing. Signed-off-by: requie <tarique.smith@gmail.com>
Cut the first release: date the changelog section, keep the version at 0.1.0 everywhere, and record the raised action pins. Signed-off-by: requie <tarique.smith@gmail.com>
The test copied the real changelog, which after a release cut has nothing under Unreleased, so the bump correctly refused. The copy now seeds one entry first, so the test exercises the bump on any tree state. Signed-off-by: requie <tarique.smith@gmail.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
Cuts the first release,
caap-benchmark 0.1.0, implementing the CAAP2.0.0-draft.1working taxonomy. Merging this PR does not publish anything; the tagv0.1.0pushed to the merge commit afterwards triggers the release workflow, which builds and publishes the GitHub release.Three commits:
fix: the release script'sbumprefused to run whenpyproject.tomlalready carried the requested version, which is exactly the state of a first release. It now validates everything before writing anything, treats an already-set version as a no-op substitution, and refuses only when the changelog already has a section for that version or has nothing to release.chore: release 0.1.0: dates the changelog section## [0.1.0] - 2026-09-30, leaves an empty[Unreleased]placeholder, adds a one-line preface for the first release, and records the action pins raised by the Dependabot merge. The version was already0.1.0inpyproject.toml,versions.py, and the README, so those files are unchanged.test: the test that bumps a copy of the real files now seeds an unreleased entry first, since a freshly cut tree has nothing under[Unreleased].Pattern or implementation impact
None. No code paths other than the release script change; no pattern, case, registry, schema, or generated file changes.
Safety impact
No test content changes.
Validation
jsonschema, 94 with 8 skipped without itpython3 scripts/release.py check 0.1.0 --tag v0.1.0reports readypython3 scripts/release.py notes 0.1.0renders the release body from the dated section