di-sukharev / di-sukharev/opencommit
update version 2.0.0
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7.5k
- Forks
- 445
- Avg merge
- 18m
- Merged PRs (30d)
- 2
Description
Hello
I try to upgrade my current version to the new 2.0.0 but no matter what I try, I always get stuck on version 1.1.50
I tried npm install -g opencommit and also npm update -g opencommit
No errors happen, everything good, but when checking opencommit --version, I still get 1.1.50 back.
Is there something broken with the npm package reporting wrong version?
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
No source files or tests are named. Reproduce the global npm install and update commands, then compare the published package metadata with the version reported by opencommit --version; this is done when installing version 2.0.0 reports 2.0.0 consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli, release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100