Npm version conflicts when lts versions are tagged
Open
- Dominant language
- JavaScript
- Stars
- 77
- Forks
- 83
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 37
Description
This issue has no description.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the npm versioning and LTS tagging workflow related to this issue. Reproduce the version conflict and identify the expected version and tag outcome; done means LTS tagging no longer produces conflicting npm versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100