ci: add Dependabot config for GitHub Actions updates#2
Merged
Conversation
Keep the SHA-pinned actions in the workflows current — pins otherwise go stale silently, with no signal when an action ships a security fix. Dependabot bumps both the SHA and its `# vX.Y.Z` comment. Scope is github-actions only (Dependabot has no Nix flake ecosystem, so flake.lock stays owned by flake-update.yml). Weekly, grouped into one batched PR, opened for manual review — consistent with the repo's no-auto-merge posture; flake-check runs on the PR via pull_request. A 7-day cooldown defers brand-new releases (supply-chain window) while still letting GHSA-driven security updates open immediately. Co-authored-by: Claude <noreply@anthropic.com>
Contributor
Author
|
boot.sh N/A |
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.
Keep the SHA-pinned actions in the workflows current — pins otherwise go stale silently, with no signal when an action ships a security fix. Dependabot bumps both the SHA and its
# vX.Y.Zcomment.Scope is github-actions only (Dependabot has no Nix flake ecosystem, so flake.lock stays owned by flake-update.yml). Weekly, grouped into one batched PR, opened for manual review — consistent with the repo's no-auto-merge posture; flake-check runs on the PR via pull_request.
A 7-day cooldown defers brand-new releases (supply-chain window) while still letting GHSA-driven security updates open immediately.
What & why
Checklist
CI runs
nix flake check(host-side guarantees, guest build, shellcheck) automatically. Thefull-boot smoke test (
tests/boot.sh) needs a real VM and is not in CI — so if your changetouches the guest, wrapper, or boot path, you must run it locally on a Nix+KVM box and paste
the result here. (See CLAUDE.md → "Definition of done".)
nix flake checkis green (CI on this PR, or run locally)bash tests/boot.shon a Nix+KVM box — pasted theN passed, M failedline below; or N/A (docs / CI-only change, no guest/wrapper/boot impact)ssh -tt)? Did a humanccvm --shellpass — resize,vim,less, vi-mode — since terminal fidelity isn't automatedCo-authored-by: Claude <noreply@anthropic.com>