Repository navigation
ci: fix the red release run and the changelog order - #38
Merged
Merged
Conversation
The release run failed on every release at "Open package version pull request": GitHub Actions may not create pull requests in this repository. The step is not needed. The release job sets the package version from the tag before it builds and publishes, so the published package and its User-Agent are correct whatever package.json on main says. The changelog job now only updates CHANGELOG.md.
The changelog updater writes a new entry above the first level-2 heading. Older minor releases used level-1 headings, so the 3.0.0 and 2.8.0 entries landed below 2.5.0. Every release heading is now level 2, newest first, under a Changelog title. The entry text is unchanged; the 2.8.0 compare link now starts at v2.7.0.
bjornftw
approved these changes
Oct 11, 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
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.
What changed
The release run no longer opens a package version pull request
Every release since v2.7.0 has ended red at "Open package version pull request": GitHub Actions is not permitted to create pull requests in this repository. Publishing itself succeeded each time.
The step is removed, together with the
npm versionstep and thepull-requests: writepermission. It is not needed: the release job checks out the tag and sets the package version from it before it builds and publishes, so the published package and itsUser-Agentare correct whateverpackage.jsononmainsays.mainkeeps a-devversion, as the Elixir SDK does.The changelog job now only updates
CHANGELOG.md, and its token permissions drop tocontents: read. The push still uses the release bot's own token.The changelog is in release order again
The changelog updater writes a new entry above the first level-2 heading. Older minor releases used level-1 headings, so the 3.0.0 and 2.8.0 entries landed below 2.5.0.
# Changelogtitle. The next entry will be written at the top.v2.7.0instead ofv2.4.1.Checks
actionlinton the workflows: no findings.🤖 Generated with Claude Code