The first run of release.yml seeded v0.0.0 on the merge commit itself, leaving zero commits between the floor and HEAD — so semantic-release correctly reported nothing to release. HEAD^ is the fix.
The tag has already been moved to 6fb7b5e by hand, so merging this PR is what cuts v0.0.1.
This still needs PACKAGE_TOKEN to have write:repository — see the PR discussion. semantic-release core dry-run-pushes to the release branch as a permission check, and that returned 403 with the current token.
The first run of `release.yml` seeded `v0.0.0` on the merge commit itself, leaving zero commits between the floor and HEAD — so semantic-release correctly reported nothing to release. `HEAD^` is the fix.
The tag has already been moved to `6fb7b5e` by hand, so merging this PR is what cuts **v0.0.1**.
**This still needs `PACKAGE_TOKEN` to have `write:repository`** — see the PR discussion. semantic-release core dry-run-pushes to the release branch as a permission check, and that returned 403 with the current token.
The floor tag marks what has already been released, so tagging the
commit being pushed leaves nothing between the floor and HEAD --
semantic-release then correctly reports there is nothing to release.
That is what the first run did: it seeded v0.0.0 on the merge commit
itself and cut no release.
HEAD^ is the first parent, so on a merge commit it is main as it was
before the merge and everything the merge brought in is releasable.
The tag has been moved to 6fb7b5e by hand; this is so the next repo
never needs that.
logan
merged commit 186f6a5839 into main2026-08-18 03:10:31 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The first run of
release.ymlseededv0.0.0on the merge commit itself, leaving zero commits between the floor and HEAD — so semantic-release correctly reported nothing to release.HEAD^is the fix.The tag has already been moved to
6fb7b5eby hand, so merging this PR is what cuts v0.0.1.This still needs
PACKAGE_TOKENto havewrite:repository— see the PR discussion. semantic-release core dry-run-pushes to the release branch as a permission check, and that returned 403 with the current token.