-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
deps: move from @npmcli/ci-detect to ci-info #5858
Conversation
See watson/ci-info#95 for more context on achieving parity between these two modules. This changes npm to use `ci-info` instead of `@npmcli/ci-detect`. Everything that npm currently flags as a CI environment should still be doing so, so there is no breaking change there. There is going to be a subtle difference in the `ci-name` config, which nothing in npm currently looks at anyways, as well as the ci name that shows up in the default `user-agent` string. Some providers will be slightly different (i.e. circle-ci vs circleci and cirrus vs cirrus-ci)
46cda63
to
c661789
Compare
no statistically significant performance changes detected timing results
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one very minor nit you can take or leave, but this looks good otherwise
@@ -442,7 +441,7 @@ define('ci-name', { | |||
description: ` | |||
The name of a continuous integration system. If not set explicitly, npm | |||
will detect the current CI environment using the | |||
[\`@npmcli/ci-detect\`](https://npm.im/@npmcli/ci-detect) module. | |||
[\`ci-info\`](https://npm.im/@npmcli/ci-info) module. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Invalid URL for ci-info. https://npm.im/ci-info
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fiddlesticks. search and replace failed me, sorry about that.
this file is the source of truth, changing it and running snapshots will fix the rest.
See watson/ci-info#95 for more context on
achieving parity between these two modules.
This changes npm to use
ci-info
instead of@npmcli/ci-detect
.Everything that npm currently flags as a CI environment should still be
doing so, so there is no breaking change there.
There is going to be a subtle difference in the
ci-name
config, whichnothing in npm currently looks at anyways, as well as the ci name that
shows up in the default
user-agent
string. Some providers will beslightly different (i.e. circle-ci vs circleci and cirrus vs cirrus-ci)