Skip to content

ci: move the release tools out of the .github folder - #343

Merged
dhensby merged 1 commit into
tediousjs:masterfrom
dhensby:ci/move-release-tools
Nov 20, 2026
Merged

dhensby merged 1 commit into
tediousjs:masterfrom
dhensby:ci/move-release-tools

Conversation

@dhensby

@dhensby dhensby commented Nov 20, 2026

Copy link
Copy Markdown
Collaborator

#338 put the release tools (semantic-release and its plugins) in .github/release/. That location has two problems, so this moves them to tools/release/.

The package and lockfile move unchanged. The release job, the Dependabot directory and .gitignore point to the new folder. Lint, the type check and the build don't pick up tools/.

I checked in a scratch clone with a local origin. semantic-release runs from tools/release and computes the next version and notes. publish.sh then pushes v4 with 7 files and nothing from tools/ or node_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: or feat: PR.

🤖 Generated with Claude Code

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
dhensby marked this pull request as ready for review November 20, 2026 21:02
@dhensby
dhensby merged commit 072fd5b into tediousjs:master Nov 20, 2026
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant