ci: harden publish workflow#4674
Open
tmm wants to merge 4 commits into
Open
Conversation
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
tmm
force-pushed
the
tmm/ci-safe-publish-workflow
branch
4 times, most recently
from
ee4018b to
6b3b1f5
Compare
commit: |
tmm
force-pushed
the
tmm/ci-safe-publish-workflow
branch
2 times, most recently
from
96b040e to
d950e5a
Compare
tmm
force-pushed
the
tmm/ci-safe-publish-workflow
branch
from
d950e5a to
7153de8
Compare
…orkflow # Conflicts: # src/jsr.json
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Harden the publish workflow by splitting versioning from manual-gated npm publishing, disabling dependency cache on release-sensitive installs, and removing unused JSR publishing.