Repository navigation
ci: move the release tools out of the .github folder - #343
Merged
Merged
Conversation
Keeping the release tools in .github/release caused two problems: - Dependabot can't open pull requests that change files under .github/ for the npm ecosystem. Its first run with the new directory failed with "invalid or unauthorized changes" for both updates in that folder, while the updates for the main package went through. - publish.sh removes .github before it builds the major tag, and it runs during semantic-release's publish step. It would therefore delete the release tools while semantic-release was still running from them. Move them to tools/release, and update the release job, the Dependabot directory and .gitignore to match. The package and lockfile don't change. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
dhensby
marked this pull request as ready for review
November 20, 2026 21:02
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.
#338 put the release tools (semantic-release and its plugins) in
.github/release/. That location has two problems, so this moves them totools/release/.conventionalcommitspreset) with400 The request contains invalid or unauthorized changes. The PRs for the main package from the same run went through. Dependabot rejects npm changes under.github/. This isn't documented, but npm: every create_pull_request returns 400 "invalid or unauthorized changes", surfaced as dependency_file_not_supported (regression; same config worked until 2026-05-18) dependabot/dependabot-core#15721 reports the same error for a.github/semantic-releasefolder, and moving the folder out of.github/fixed it for others there.publish.shwould delete them mid-release.publish.shruns in semantic-release's publish step and removes.githubbefore it builds the major tag. With the tools in.github/release/node_modules, it would delete them while semantic-release was still running from them, before thesuccessstep. Nothing has released since ci: harden the release pipeline #338, so this hasn't happened yet.The package and lockfile move unchanged. The release job, the Dependabot directory and
.gitignorepoint to the new folder. Lint, the type check and the build don't pick uptools/.I checked in a scratch clone with a local
origin. semantic-release runs fromtools/releaseand computes the next version and notes.publish.shthen pushesv4with 7 files and nothing fromtools/ornode_modules, and the release tools are still on disk afterwards.The action itself doesn't change, so this doesn't release. It should merge before the next
fix:orfeat:PR.🤖 Generated with Claude Code