Publish with provenance statements #6602
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
kneth
added
no-jira-ticket
elle-j
approved these changes
Apr 9, 2024
There was a problem hiding this comment.
LGTM after adding a "repository" (and likely a nested "directory" as well) to babel-plugin/package.json (and possibly also to fetch/package.json, but unsure if it will actually be needed there if it's only used internally).
kneth
force-pushed
the
kneth/publish-with-provenance
branch
from
152f12b
to
e1e4062
Compare
kraenhansen
approved these changes
Apr 11, 2024
|
Testing it by releasing an rc (#6608) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What, How & Why?
Following this guide as it seems to be simple 😄
☑️ ToDos
Compatibilitylabel is updated or copied from previous entryCOMPATIBILITY.mdpackage.jsons (if updating internal packages)Breakinglabel has been applied or is not necessary