Repository navigation
Description
Summary: The zizmor check is failing on 3 open pull requests in projectbluefin/server at the same time. When one check fails on this many pull requests, the cause is usually shared (the base branch, a workflow, a pinned action or the runner image), not any single change. The hive opened this issue so the failure is looked at once, here, instead of once per pull request.
Evidence
- Check:
zizmor - Open pull requests failing it (3): test: install a network-booted server from its own screen, and check unknown firmware keys refuse to start it #644, fix: widen dogfood installer per-key gap under console noise #647, feat(homelab): add HOMELAB_GATEWAY_ISSUER for the Gateway certificate issuer #653
- Default branch: the newest run of this check on the base branch is not red. Either these pull requests are behind their base, or something outside the branch changed since that run (a moved action tag, a new runner image, an upstream outage).
Log excerpt from the failing runs:
unit-tests.yml:45: action's hash pin has mismatched or missing version comment: tag points to commit cfdb7ed4ccc7
track-junctions.yml:45: action's hash pin has mismatched or missing version comment: tag points to commit cfdb7ed4ccc7
reproducibility.yml:64: action's hash pin has mismatched or missing version comment: tag points to commit cfdb7ed4ccc7
build.yml:297: action's hash pin has mismatched or missing version comment: tag points to commit cfdb7ed4ccc7
build.yml:222: action's hash pin has mismatched or missing version comment: tag points to commit cfdb7ed4ccc7
build.yml:182: action's hash pin has mismatched or missing version comment: tag points to commit cfdb7ed4ccc7
build.yml:142: action's hash pin has mismatched or missing version comment: tag points to commit cfdb7ed4ccc7
Next step
Repair the shared cause once, usually with one pull request against the base branch or the shared workflow, then close this issue. Pull requests that are only behind their base may also need their branch updated.
The hive keeps this description in step with the failing pull requests while the failure lasts (edits do not notify) and does not comment on the pull requests listed here.
Activity
jeefy commentedon Nov 16, 2026
Issue triage
Next action: a triager or maintainer reviews this issue.
Reporter or contributor
kind/*label is set, categorize the issue with one of:/kind bug,/kind regression,/kind security,/kind feature,/kind documentationor/kind cleanup./area <area>if this repository supports area labels; use a value from its label list.Triager or maintainer
/triage accepted. Only triagers and maintainers can do this; acceptance does not assign an implementer.needs-kindclears when a kind is set.needs-triageand this post clear when triage is accepted.See Triage & Prow Commands for all available commands.
hivecommons-hive commentedon Nov 16, 2026
🌱 Good first issue — bring your own coding agent
Hi! This repository is maintained with hive and welcomes contributions made with your own AI coding agent (Claude Code, Codex, Copilot CLI, Bob, …). hosted-projectbluefin-knuckle-gjvq picked this issue as a good place to start because:
How to land it (no waiting on a human):
git commit -s).Fixes #683— that closing keyword is how hive's contributor lane links the PR to your claim.Paste this to your agent
Prefer not to drive the loop by hand? Run your own hive (we call them clankers) — a relay on your machine that claims, opens the PR and handles review fixes for you, and earns you a contributor profile and a leaderboard place: see https://hosted-projectbluefin-common-nmq5.hive.hivecommons.dev/contribute.
If nobody claims it, hive may pick it up itself — claiming first prevents that. Docs: contributor relay · contributor lane auto-merge · trust tiers · AGENTS.md.
Danathar commentedon Nov 17, 2026
Triage: not accepting. There's nothing to fix on
main.zizmor(inlint-actions.yml) passes onmain: its last three runs succeeded, the newest at ab7f54f. The three PRs fail it because they're behindmain. Their last commits are from 11-09 to 11-12, and since then Renovate moved thetaiki-e/install-actionpin twice (#671, #676). The PR branches still have the older pin and version comment that zizmor rejects. Updating #644, #647 and #653 to currentmainshould clear it, and then this tracker can close.