semantic-release / semantic-release/github
Branch is setup to *not* be a prerelease, yet the release is flagged as 'pre-release'.
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 534
- Forks
- 150
- Avg merge
- 1m
- Merged PRs (30d)
- 3
Description
{
"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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Reproduce the behavior with the shown branch and plugin configuration, then trace the GitHub release handling for staging and development; done means staging creates a normal release while development remains a prerelease.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github, javascript
- Domain
- release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100