fix: swap out @npmcli/ci-detect
for ci-info
#667
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🧰 Changes
I opened npm/ci-detect#47 to address this, but per #664 it looks like our CI detection has some imperfections.
ci-info
seems to be more popular and well-maintained. We looked at this package ages ago but I was initially hesitant because it is a bit annoying to write tests with it but I got that figured out.Update: it looks like the npm CLI team is planning on deprecating their package in favor of
ci-info
, so we should probably do this anyways.🧬 QA & Testing
No material changes here except perhaps better CI detection. Do tests pass?