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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The publish job now checks out with
secrets.GITHUB_TOKEN. Unless repository settings explicitly grant that tokencontents: write, the default permission is read‑only, so the latergit pushin the same job will be rejected and the version‑bump commit will never land. The previoussecrets.TOKENwas presumably a PAT with the necessary rights. Consider restoring a PAT or addingpermissions: contents: writefor the job before relying onGITHUB_TOKENfor the push.Useful? React with 👍 / 👎.