Skip to content

[shared-ci] zizmor failing across projectbluefin/server #683

Open

Description

@hivecommons-hive

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

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

  1. added
    kind/bugSomething is broken.
    agent/ci-maintainerFiled or owned by the ci-maintainer agent.
    origin/governorFiled by the Hive governor/automation on its own behalf (provenance only, not routing or hold)
    on Nov 16, 2026
  2. jeefy commented on Nov 16, 2026

    @jeefy
    Collaborator

    Issue triage

    Next action: a triager or maintainer reviews this issue.

    Reporter or contributor

    • If no kind/* label is set, categorize the issue with one of: /kind bug, /kind regression, /kind security, /kind feature, /kind documentation or /kind cleanup.
    • Optionally add an area with /area <area> if this repository supports area labels; use a value from its label list.

    Triager or maintainer

    • Review the report and ask the reporter for any missing information.
    • When the scope is accepted and the issue is ready for work, comment /triage accepted. Only triagers and maintainers can do this; acceptance does not assign an implementer.

    needs-kind clears when a kind is set. needs-triage and this post clear when triage is accepted.

    See Triage & Prow Commands for all available commands.

  3. hivecommons-hive commented on Nov 16, 2026

    @hivecommons-hive
    ContributorAuthor

    🌱 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:

    • a concrete, reproducible bug report
    • has clear steps or acceptance criteria

    How to land it (no waiting on a human):

    1. Claim it through the relay: open https://hosted-projectbluefin-common-nmq5.hive.hivecommons.dev/contribute?issue=projectbluefin%2Fserver%23683 and sign in with GitHub. Claiming stamps the issue so hive leaves it to you.
    2. Fork or branch, make the change with your agent, and sign each commit with DCO (git commit -s).
    3. Open a PR whose description says Fixes #683 — that closing keyword is how hive's contributor lane links the PR to your claim.
    4. Hive runs CI and merges green PRs from claimed contributors automatically.
    Paste this to your agent
    Fix #683 in github.com/projectbluefin/server (https://github.com/projectbluefin/server/issues/683). First open https://hosted-projectbluefin-common-nmq5.hive.hivecommons.dev/contribute?issue=projectbluefin%2Fserver%23683 and claim the issue through the hive relay (sign in with GitHub). Work on a fork/branch; keep the change scoped to the issue; sign every commit with DCO (git commit -s); open a PR whose description contains the line 'Fixes #683' so the hive's contributor lane can auto-merge it once CI is green. Read and follow https://github.com/projectbluefin/server/blob/HEAD/AGENTS.md before changing code.
    

    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.

  4. added
    good first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on Nov 16, 2026
  5. Danathar commented on Nov 17, 2026

    @Danathar
    Contributor

    Triage: not accepting. There's nothing to fix on main.

    zizmor (in lint-actions.yml) passes on main: its last three runs succeeded, the newest at ab7f54f. The three PRs fail it because they're behind main. Their last commits are from 11-09 to 11-12, and since then Renovate moved the taiki-e/install-action pin twice (#671, #676). The PR branches still have the older pin and version comment that zizmor rejects. Updating #644, #647 and #653 to current main should clear it, and then this tracker can close.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent/ci-maintainerFiled or owned by the ci-maintainer agent.good first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/bugSomething is broken.needs-triageMissing required label matching ^triage/origin/governorFiled by the Hive governor/automation on its own behalf (provenance only, not routing or hold)stage/015-triage-neededActionable but held by the reporter-trust gate: awaiting a maintainer's triage labelstage/stalledIn its current stage longer than expected

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions