search

fabiospampinato / bump

Bump updates the project's version, updates/creates the changelog, makes the bump commit, tags the bump commit and makes the release to GitHub. Opinionated but configurable.
MIT License
412 stars 13 forks source link

Version 1.2.2 npm broken #33

Closed tylerclark closed 1 year ago

tylerclark commented 1 year ago

Not sure what happened but 20 hours ago the following command no longer works: npm install @fabiospampinato/bump@1.2.2 -g

Error:

npm ERR! code 128
npm ERR! An unknown git error occurred
npm ERR! command git --no-replace-objects ls-remote ssh://git@github.com/fabiospampinato/Caporal.js.git
npm ERR! Warning: Permanently added 'github.com' (ED25519) to the list of known hosts.
npm ERR! git@github.com: Permission denied (publickey).
npm ERR! fatal: Could not read from remote repository.
npm ERR! 
npm ERR! Please make sure you have the correct access rights
npm ERR! and the repository exists.
fabiospampinato commented 1 year ago

Versions below v3 are dead and not supported anymore.

tylerclark commented 1 year ago

Wow. Way to kill our pipeline without notice. npm packages are versioned for a reason.

fabiospampinato commented 1 year ago

Sorry about that, I didn't realize that deleting my fork of Caporal would have much an impact (v1 installed that from github rather than the registry). Just upgrading to v3 should be better anyway, it's faster, it has no third-party dependencies whatsoever. If you find issues with that then I'm happy to help.

tylerclark commented 1 year ago

v3 doesn't even work.

$ bump patch
✖ Version bump failed

Error: Unable to update version in package-lock.json file
fabiospampinato commented 1 year ago

Can you post a little repro? Mainly seeing the package.json and package-lock.json files for that repo should uncover the issue.