Repository navigation
chore: migrate registry branch to eventctl v2 - #2
Merged
Merged
Conversation
* Publish act-backed starter baseline * Use complete checkout cache for act * Fetch complete checkout tree for act * Build a deterministic act action cache * Seed act fixture refs without push transport * Provide a token to act checkout fixtures * Map the act host gateway on Linux * Advertise main in the act fixture remote * Seed act refs from shallow checkouts * Route request validators by changed path * feat: migrate starter to eventctl v2 * test: resolve pinned eventctl release in e2e * docs: use the release lock asset * chore: pin eventctl v0.2.0 * test: support hosted amd64 act fixtures
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.
Aligns the protected registry branch with the published v2 main tree. The current v1 registry validator will reject this intentionally; after merge, the v2 registry workflow validates the v2 state on push.