Commitlint: Error during Travis runs: `No matching version found for @commitlint/rules@^8.1.0`

Created on 15 Jul 2019  路  6Comments  路  Source: conventional-changelog/commitlint

We've been using commitlint in our Travis runs successfully for a number of months now. Over the last few minutes, our Travis runs are failing:

$ npm install @commitlint/travis-cli -D
npm ERR! code ETARGET
npm ERR! notarget No matching version found for @commitlint/rules@^8.1.0
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget 
npm ERR! notarget It was specified as a dependency of '@commitlint/lint'
npm ERR! notarget 
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/travis/.npm/_logs/2019-07-15T19_10_49_725Z-debug.log
The command "npm install @commitlint/travis-cli -D" exited with 1.

Version 8.1.0 is available @ https://www.npmjs.com/package/@commitlint/rules/v/8.1.0.

So there must a be a minor misconfiguration somewhere.

Most helpful comment

@byCedric It's all working now with 8.1.0 (I've tested across three of our repos) so I'm closing this issue. Thanks for the feedback in the meantime.

All 6 comments

Hi @myii, thanks for your quick issue report. We've just released version 8.1.0 of Commitlint, and I think the (cached) registries still need to update this part. As you spotted correctly, version 8.1.0 for @commitlint/rules is actually published already.

I'll monitor this and see if it's a persistent issue. If it's not fixed, I'll contact NPM about this.

Meanwhile, is this issue still there after some retries? I think it might update the local/cached/proxy registry after the failures.

@byCedric I was thinking the same thing. I'll retry a few more times or I'll pin to 8.0.0 in the meantime until this settles down. Thanks for the prompt response!

I'm sorry for the trouble!

No problem, I'll take this opportunity to thank you all for providing these excellent packages.

I've pinged NPM about this and pinned this issue, other registries are still not updated. Again, sorry for the trouble, this should be resolved soon. If you encounter the same issue, pin the version to 8.0.0 or try retrying it.

@byCedric It's all working now with 8.1.0 (I've tested across three of our repos) so I'm closing this issue. Thanks for the feedback in the meantime.

Was this page helpful?
0 / 5 - 0 ratings