chore: move publish to its own workflow and add sigstore provenance #248
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
This pulls the actual publication of the module into its own workflow, which is run when a release is created. It also adds sigstore provenance to the publication so that the release is signed by sigstore and logged in a public transparency ledger. See: https://docs.npmjs.com/generating-provenance-statements See: https://www.sigstore.dev/ Signed-off-by: Lance Ball <lball@redhat.com>
lance
added
enhancement
Codecov ReportPatch and project coverage have no change.
Additional details and impacted files@@ Coverage Diff @@
## main #248 +/- ##
=======================================
Coverage 90.34% 90.34%
=======================================
Files 9 9
Lines 290 290
=======================================
Hits 262 262
Misses 28 28 ☔ View full report in Codecov by Sentry. |
|
@lholmquist ptal |
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.
This pulls the actual publication of the module into its own workflow, which is run when a release is created. It also adds sigstore provenance to the publication so that the release is signed by sigstore and logged in a public transparency ledger.
See: https://docs.npmjs.com/generating-provenance-statements
See: https://www.sigstore.dev/