Version 1.3.0 was never released
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.2k
- Forks
- 97
- Avg merge
- 15d 21h
- Merged PRs (30d)
- 1
Description
See title, version 1.3.0 never reached github releases nor npm:
Both CI runs failed (logs are gone):
Contributor guide
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 reviewing pull request 261 and the two failed CI runs linked in the issue, focusing on the release workflow and its available configuration. Determine why the 1.3.0 release did not publish, then verify that the version appears in GitHub Releases and npm.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript
- Domain
- ci-cd, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100