Which PR is it? I still have the same problem with the latest version.
Speaking of latest version, the current 1.1.36 on npm seems to be published incorrectly. When you install it with npm i opencommit@1.1.36 and then do oc --version, it shows as 1.1.35.
There’s probably a mistake made during packaging. Maybe it’s time to consider using GitHub Actions.
should be fixed with a coming PR, thanks ❤️
we tried 3 PRs and nothing healed it, if anybody wants to be the HERO who solves this — please do the shot and save us here 🙏 🦺
should be fixed now, pls update
npm i -g opencommit@di-sukharev I’m going to tackle this topic, I’ll give it a try.
@di-sukharev
Which PR is it? I still have the same problem with the latest version.
Speaking of latest version, the current 1.1.36 on npm seems to be published incorrectly. When you install it with
npm i opencommit@1.1.36and then dooc --version, it shows as 1.1.35.There’s probably a mistake made during packaging. Maybe it’s time to consider using GitHub Actions.
Wow, you’re doing a great job! @di-sukharev