semantic-release / semantic-release/github
asset options creates a untagged release that is not updated after asset upload
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 534
- Forks
- 150
- Avg merge
- 1m
- Merged PRs (30d)
- 3
Description
Without any reasonable change that I could identify from yesterday to today all our builds where failing due "Publishing untagged version"
In the above example, should had "v1.4.1"
After trying to debug a single line changes made the trick
but many failing test after this change (due urgent reasons of our build system had to fork etc)
Is there something I am missing ? (will create PR etc since I dont like forks ;) )
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
Start by reproducing the failure in the asset options path, focusing on how the GitHub release is created and updated after asset upload. Compare the untagged release shown in the report with the expected v1.4.1 release, then run the relevant test suite. Done means asset uploads update the correctly tagged release without causing regressions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, javascript
- Domain
- release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100