fix: pass releases to publish check #444
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lukekarrys
force-pushed
the
lk/abundant-brave-insect
branch
from
3fffeee
to
650d56f
Compare
wraithgar
approved these changes
May 7, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
If
publish: trueis not set, then the release intergration workflow falls back to runningnpm view $SPECwhich will error if the package has not been published. This tags the CODEOWNERS in the release issue so we know something went wrong.This doesn't have much use now that we are moving everything to
publish: truebut it would have caught a missing publish last week that I missed on@npmcli/fs: https://github.com/npm/fs/actions/runs/8946801618/job/24577963034#step:7:4The
RELEASESenv var was only being set for the publish step, not the check if published step.