Repository navigation
ci: regenerate workflows with Velnor Actions 0.1.80 - #49
Merged
Merged
Conversation
Co-authored-by: Codex <codex@openai.com> Signed-off-by: Alexey Zhokhov <alexey@zhokhov.com>
2 tasks
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.
Why
Update jackin-dev's generated GitHub Actions to released Velnor Actions 0.1.80 as part of the owner's consumer rollout.
Pin
.velnor/release-manifest.jsonmoves from 0.1.0 to 0.1.80, source commitb71a0045e42f6a8b620aa9283d0106bed622fe3b.Generation and verification
Generation exited 0 and the fresh preview matched. Both Mise gates and
git diff --checkpassed.Scope
This updates the release manifest and Velnor-owned
.githuboutputs. It does not change application behavior, generator configuration, or unrelated tool pins.Generator notes
The plan reports zero workspace crates and a required-check name transition from
Velnor / RequiredtoRequired. Its post-merge sequence says to let the new default-branch check complete before changing branch protection. Generation also reports existinggh@2.103.3andshellcheck@0.11.0installs without verification entries; those pins were left unchanged.