Conversation
Drop @semantic-release/git and @semantic-release/changelog: the main ruleset (PR required, no bypass actors) rejects the version-bump push, aborting the release before tag/publish. VSIX versioning is unaffected (semantic-release-vsce stamps package.json in the CI workspace); release notes live in GitHub Releases. CHANGELOG.md now points there.
|
🎉 This PR is included in version 2.13.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Why
The 2.13.0 release run failed at
@semantic-release/git's prepare step: it pushes a version-bump commit (CHANGELOG.md+package.json) directly tomain, which themain-defaultruleset (PR required, no bypass actors) rejects with GH013. The run aborted before tagging/publishing — no v2.13.0 tag, GitHub release, or Marketplace publish exists, so the retry is clean.What
@semantic-release/gitand@semantic-release/changelogfrom.releaserc.jsonand devDependenciesCHANGELOG.mdnow points to GitHub Releases (the plugin-written changelog was never committable under the ruleset)VSIX versioning is unaffected:
semantic-release-vscestamps the computed version intopackage.jsonin the CI workspace before packaging. Repopackage.jsonintentionally stays at the last-committed version; git tags + GitHub Releases are the source of truth.Merging this PR re-triggers the publish workflow and should cut 2.13.0 (feat commits since v2.12.0 are already on this branch).
🤖 Generated with Claude Code