Repository navigation
chore: use vendored github actions - #80
Merged
Merged
Conversation
|
Preview: https://75c42353-monoshot.broken-thunder-fb8b.workers.dev ( |
Amp-Thread-ID: T-01a1645e-4d84-76fb-8823-eeaa1c8393dd
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
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.
Use the reviewed snapshots from wevm/actions#10 for 2 action references. Preserve pinned upstream versions, inputs, permissions, triggers, and job conditions. Previously floating refs are frozen at their inventoried commits, rechecked against upstream before this PR.
For example, imported actions now use
wevm/actions/vendor/<owner>/<action>/<version>@73e899a58d51092d694fbaf94b7a1d8c09bfea28.Validation: parsed YAML differs only in the intended
usesvalues; every target and upstream SHA matches published provenance;git diff --checkpasses. Actionlint passes (shellcheck and pyflakes disabled).This does not enable repository or organization restrictions. Remaining external actions require separate migration or explicit exceptions. Deployment/release-only paths have not been executed locally.