Repository navigation
chore(release): v0.2.0 - #33
Merged
Merged
Conversation
Assisted-by: Claude Code (Claude Opus 5.5)
Projects made from v0.1.0 run the maintenance scripts from a new path. Assisted-by: Claude Code (Claude Opus 5.5)
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
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.
What changed, and why?
Release commit for the template's v0.2.0: renames
[Unreleased]inCHANGELOG.mdto[0.2.0] - 2026-10-30, adds a fresh[Unreleased], a one-paragraph summary, an AI-use statement, and the comparison links. As the template,pyproject.tomlandCITATION.cffstay at0.0.0(projects copy them).Why minor: since v0.1.0 the template adds optional parts and the
add-partskill, Zenodo citation (#31) and changed setup defaults that users can decline (#29), plus fixes and docs. One change is marked Breaking:: #26 movedtools/into.github/tools/, so projects made from v0.1.0 run the scripts from a new path afterupdate-from-template. Before 1.0, a breaking change is still a minor release.Please check
After merging
Tell the AI it's merged. It will tag
v0.2.0and push the tag, which runs the release workflow, creates the GitHub Release (notes from this changelog section) and triggers Zenodo. It asks before pushing the tag.How was it checked?
pytest: all pass. The release workflow'sawkextraction was run locally on this CHANGELOG and produces the 0.2.0 section.Scientific decisions
None.
Release impact
This is the release: minor, v0.1.0 → v0.2.0.
AI use
Claude Code (Claude Opus 5.5) prepared this release commit with the
prepare-releaseskill and drafted the summary and AI-use statement. A maintainer reviews before merging.🤖 Developed with AI assistance from Claude Code; a maintainer reviews it before merging.