v6.x not latest…?
- Dominant language
- JavaScript
- Stars
- 9
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
I just ran `npm i --save arguable`, and was surprised to find that I got **`arguable@5.2.3`**.
When I ran `npm info arguable`, I noticed the following:
```
dist-tags:
canary: 6.4.1 latest: 5.2.3
```
To me, that appears as if version 6 has been out for some time. I can’t help but wonder if you set up a publish script to make releases under `canary` and forgot to {turn them off, also add `latest`, etc.}.
* What are you using `canary` for?
* What is the intended latest version of Arguable?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the reported npm i --save arguable and npm info arguable results, then inspect the package's published dist-tags and release configuration. Confirm which version should be latest and document or correct the canary/latest setup; done when npm metadata reflects the intended release behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100