Repository navigation
ci(vulnetix): pin the Vulnetix actions at v4.24.30 - #340
Merged
Merged
Conversation
Contributor
Vulnetix config planManager
0 to create, 1 to update, 0 to delete, 0 unchanged |
v4.24.30 carries the bounded forge pass (#339). The workflow already passes --forge-window-days, which the v4.24.3 CLI does not know.
0x73746F66
force-pushed
the
ci/vulnetix-actions-v4.24.30
branch
from
November 13, 2026 15:31
6b59a5a to
46e702d
Compare
Contributor
Vulnetix config planManager
0 to create, 1 to update, 0 to delete, 0 unchanged |
This was referenced Nov 13, 2026
fix(analyze): a spent GitHub quota at preflight skips the forge pass instead of failing the run
#341
Merged
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.
What
Moves every
Vulnetix/cli/*action in.github/workflows/vulnetix.ymlfromv4.24.3tov4.24.30. The workflow was regenerated withvulnetix gha init --ref v4.24.30, andactions.lockwas relocked withgh actions-lock --no-narrow.Why
#339 made the analyze job pass
--forge-window-days=7on a push or a release. The pinned v4.24.3 CLI does not know that flag, so the analyze step exited early on main. v4.24.30 contains the flag and the forge budget that keeps half the token quota, so with this pin the quota fix takes effect in this repository.How verified
gh actions-lock --ignore-local-actions --verify-local: all 12 workflows have complete lockfile coverage.actionlint .github/workflows/vulnetix.ymlpasses.vulnetix gha init --check --ref v4.24.30reports the workflow is current.action-lib/cli-releaseresolves to a published binary.