Skip to content

Semantic release workflow fails due to main branch requiring a pull request for changes #642

Description

@jrpdango

Semantic release functionality was recently added in #633, but the first attempted workflow run failed due to a main branch rule requiring changes to be done through pull requests.

This is because the workflow needs to git push --tags to main to create a release.

Suggested solution

We likely need to update the Release workflow to use the Personal Access Token (PAT) of a user with rule bypass permissions instead of just the inbuilt GITHUB_TOKEN (see docs). Also tested on my fork.

I can make the changes to the workflow file, but the PAT itself will have to be set as a repo secret by someone with the appropriate privileges.

Side note

(I can make another issue/discussion for this if necessary.)

Apparently the semantic-release team doesn't actually recommend using the @semantic-release/git plugin to make commits every release.

Unless we need CHANGELOG.md, we can probably just remove the @semantic-release/git and @semantic-release/changelog plugins since it would be redundant with the /releases page of this repo anyway. Doing this won't add a commit every workflow run, though we'd still need the PAT regardless to create releases.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions