chore: recover version drift to v0.0.3 and seed CHANGELOG#123
Merged
Conversation
The release workflow's 'Commit version bump' step was gated to workflow_dispatch only, so the tag-push releases v0.0.2 and v0.0.3 never wrote the bumped plugin.json / marketplace.json back to main, and the post-release CHANGELOG step left a dangling 'changelog/<tag>' PR each time. As a result main has been frozen at 0.0.1 with no CHANGELOG since the first release. This commit: - Bumps plugin.json and .github/plugin/marketplace.json (metadata.version and the git-ape plugin entry) to 0.0.3, matching the latest shipped tag. - Adds CHANGELOG.md with reconstructed entries for v0.0.2 and v0.0.3. - Leaves ape-context at 1.0.0 and website/package.json untouched.
Contributor
|
sendtoshailesh
approved these changes
May 26, 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
2 participants
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.
Why
The release workflow's
Commit version bumpstep was gated toworkflow_dispatchonly (git-ape-release.yml#L100), so the tag-push releases for v0.0.2 and v0.0.3 never wrote the bumpedplugin.json/.github/plugin/marketplace.jsonback tomain. The post-release CHANGELOG step likely opened achangelog/<tag>PR each time that was never merged.As a result
mainhas been frozen at0.0.1with noCHANGELOG.mdsince the first release, even though v0.0.3 shipped on 2026-05-13.What
plugin.json→0.0.3.github/plugin/marketplace.json:metadata.version→0.0.3plugins[name=git-ape].version→0.0.3plugins[name=ape-context]left at its own1.0.0CHANGELOG.mdwith reconstructed entries forv0.0.2andv0.0.3(and a stub forv0.0.1)website/package.jsonis intentionally untouched (docs versioning is decoupled)Workflow fix
The underlying bug in
.github/workflows/git-ape-release.yml(it now re-applies the bump against the freshmaintree inside the same step that writes the CHANGELOG, so tag-push releases land both files together) is on a separate branch and will follow as its own PR.Validation
The plugin version check workflow (
.github/workflows/git-ape-plugin-version-check.yml) should pass on this PR.