-
Notifications
You must be signed in to change notification settings - Fork 23
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
bump make-fetch-happen to v13 #681
Conversation
🦋 Changeset detectedLatest commit: 7181198 The changes in this PR will be included in the next version bump. This PR includes changesets to release 9 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
--- | ||
'@sigstore/mock': minor | ||
'@sigstore/cli': minor | ||
--- | ||
|
||
Drop node 14 support |
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.
Since these two packages haven't yet reached a stable 1.0 release, I'm NOT going to treat the node 16 requirement as a major change.
return promise | ||
.promiseAny(providers.map((getToken) => getToken(this.audience))) | ||
.catch(() => Promise.reject('CI: no tokens available')); | ||
return Promise.any( | ||
providers.map((getToken) => getToken(this.audience)) | ||
).catch(() => Promise.reject('CI: no tokens available')); |
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.
Now that we're on Node 16 we can swap our custom promiseAny
function for the Promise.any
implementation in the standard library.
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.
💯
Signed-off-by: Brian DeHamer <[email protected]>
Signed-off-by: Brian DeHamer <[email protected]>
Signed-off-by: Brian DeHamer <[email protected]>
Summary
Preparation for the inclusion of
sigstore
in the v10 release of the npm CLI.To minimize the number of extra dependencies we bring to the npm CLI integration, we keep our version of the
make-fetch-happen
package synchronized with the version in use by npm. With their v10 release, npm will move to[email protected]
so we need asigstore
version which does the same.The move from v11 to v13 of
make-fetch-happen
is a MAJOR SEMVER change which drops support for node 14 (EOL'd April 2023). Adopting v13 ofmake-fetch-happen
insigstore
will also trigger a major semver change and necessitates that we also drop support for node 14.The changes here include:
make-fetch-happen
to v13 in the packages which are dependent on itThere will be a similar change made to the
tuf-js
package which also depends onmake-fetch-happen
.See #523