Repository navigation
Date the 0.1.0 changelog entry for release - #5
Merged
Merged
Conversation
`release-checks` in publish.yml rejects a tag whose changelog heading is not dated, so `## [0.1.0] - Unreleased` becomes `## [0.1.0] - 2026-10-27` and a fresh `## [Unreleased]` section opens above it for the next cycle. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
philtgun
approved these changes
Oct 27, 2026
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.
Prepares the repository for the
v0.1.0tag.What this changes
CHANGELOG.mdonly — the0.1.0heading gains its release date and a fresh## [Unreleased]section opens above it:No code, no version bump.
src/audioshake/_version.pystays at0.1.0.Why
release-checksin.github/workflows/publish.ymlrejects a tag whosechangelog heading carries no
YYYY-MM-DDdate, sov0.1.0cannot publishwhile the heading reads
Unreleased.Verified by running the workflow's own gate code against the edited file:
After this merges
audioshakedoesnot exist on PyPI yet, so there is no project to attach a normal trusted
publisher to (owner
audioshake, repoaudioshake-python, workflowpublish.yml, environmentpypi).git tag v0.1.0 && git push origin v0.1.0audioshake/claude-pluginsmarketplacereftov0.1.0— theplugin is at 0.3.11 on this branch.
🤖 Generated with Claude Code