Branch is setup to *not* be a prerelease, yet the release is flagged as 'pre-release'.

{
  "branches": [
    {
      "name": "main",
      "prerelease": false
    },
    {
      "name": "development",
      "prerelease": true
    },
    {
      "name": "staging",
      "prerelease": false
    }
  ],
  "plugins": [
    "@semantic-release/commit-analyzer",
    "@semantic-release/release-notes-generator",
    "@semantic-release/github"
  ]
}

This config does not throw an error, but behaves inconsistent. Pushing to staging does not create a release, but a pre-release.

[diogokiss]

Same here. 😢

[aslafy-z]

It may be due to this check: https://github.com/semantic-release/github/blob/master/lib/is-prerelease.js#L1. It tags as pre-release any branch marked as pre-release, or any branch marked as release and not tagged as main. As per https://github.com/semantic-release/semantic-release/blob/971a5e0d16f1a32e117e9ce382a1618c8256d0d9/lib/branches/normalize.js#L87, it looks like there can be only one main tagged branch, thus, only one branch not beeing used as pre-release (in the case of the GitHub plugin). I was not able to find references with multiple main branches, see https://github.com/semantic-release/semantic-release/blob/971a5e0d16f1a32e117e9ce382a1618c8256d0d9/test/branches/normalize.test.js#L150.

This issue was introduced with https://github.com/semantic-release/github/pull/235.

Possible workaround

In my case I’m defining two branches objects:

  branches: [
    'release/+([0-9])?(.{+([0-9]),x}).x',
    'master',
  ],

Moving the master branch first should prevent pre-releases from being created for this branch.