Review backlog (correctness): Renovate git-refs tracking races against upstream image publish #565

Activity

1. hivecommons-hive

   added

   agent/reviewerCreated by Hive for agent-filed issue provenanceCreated by Hive for agent-filed issue provenance

   on Oct 28, 2026
2. jeefy

   added

   needs-kindMissing required label matching ^kind/Missing required label matching ^kind/

   on Oct 28, 2026
3. jeefy commented on Oct 28, 2026

   

   jeefy

   on Oct 28, 2026

   Collaborator

   More actions

   Please set a kind: /kind bug, /kind feature, /kind cleanup, /kind documentation, /kind regression or /kind security.

   See Triage & Prow Commands for all available commands.
4. jeefy

   added

   needs-triageMissing required label matching ^triage/Missing required label matching ^triage/

   on Oct 28, 2026
5. jeefy commented on Oct 28, 2026

   

   jeefy

   on Oct 28, 2026

   Collaborator

   More actions

   To accept this issue, comment /triage accepted. To categorize, comment /area <area> or /kind <kind>.
6. Danathar

   added

   triage/acceptedScope accepted; ready for work. Use `/triage accepted`.Scope accepted; ready for work. Use `/triage accepted`.

   kind/bugSomething is broken.Something is broken.

   and removed

   needs-kindMissing required label matching ^kind/Missing required label matching ^kind/

   needs-triageMissing required label matching ^triage/Missing required label matching ^triage/

   on Oct 28, 2026
7. Danathar commented on Oct 28, 2026

   

   Danathar

   on Oct 28, 2026

   Contributor

   More actions

   Triage: accepted (kind/bug). Valid low-severity Renovate tracking race; worth fixing before it bites a release.
8. hivecommons-hive

   added

   approved-direction

   stage/010-actionableTriaged; eligible for the hive to pick upTriaged; eligible for the hive to pick up

   on Oct 28, 2026
9. hivecommons-hive commented on Oct 28, 2026

   

   hivecommons-hiveBot

   on Oct 28, 2026 – with hivecommons-hive

   ContributorAuthor

   More actions

   🌱 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
   • short, focused description

   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%23565 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 #565 — 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 #565 in github.com/projectbluefin/server (https://github.com/projectbluefin/server/issues/565). First open https://hosted-projectbluefin-common-nmq5.hive.hivecommons.dev/contribute?issue=projectbluefin%2Fserver%23565 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 #565' 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.
10. hivecommons-hive

    added

    good first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.Denotes 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.Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

    hive/claimed-by-scanner

    stage/020-claimedClaimed by the scanner or a relay contributorClaimed by the scanner or a relay contributor

    and removed

    stage/010-actionableTriaged; eligible for the hive to pick upTriaged; eligible for the hive to pick up

    on Oct 28, 2026
11. hivecommons-hive commented on Oct 28, 2026

    

    hivecommons-hiveBot

    on Oct 28, 2026 – with hivecommons-hive

    ContributorAuthor

    More actions

    🛠️ Hive agent scanner (hive hosted-projectbluefin-knuckle-gjvq) started work on this issue at 2026-10-28T17:38:42Z. A pull request referencing this issue supersedes this mark; it lapses on its own at 2026-10-28T19:38:42Z if none appears.
12. hivecommons-hive

    added

    stage/040-covered-by-prAn open PR covers this issueAn open PR covers this issue

    and removed

    stage/020-claimedClaimed by the scanner or a relay contributorClaimed by the scanner or a relay contributor

    on Oct 28, 2026
13. hivecommons-hive commented on Oct 28, 2026

    

    hivecommons-hiveBot

    on Oct 28, 2026 – with hivecommons-hive

    ContributorAuthor

    More actions

    Additional finding (folded in — same finding area and category). Raised in the Hive review of PR #548 (#548) and folded into this issue because it is a correctness finding at the same symbol or lines of renovate.json as this issue. Address it together with this issue; if it turns out to be a different problem, file it separately before closing.

    Review backlog (correctness): Renovate git-refs tracking races upstream image publish

    • Renovate git-refs tracking races upstream image publish (renovate.json:31)

    Perspective: correctness
    Severity: low (P3)
    Evidence: renovate.json:31 (

    server/renovate.json

    Line 31 in 6041d60

    "customType": "regex",

    )
    Finding: Renovate git-refs tracking races upstream image publish

    renovate.json:31-43 tracks upstream master via git-refs, so any upstream merge whose image pipeline fails (e.g. 2998809721 for 2232beb) produces a PR pinning a tag that does not exist in the registry and fails validate. Pre-existing, not changed by this PR; backlog to gate on image existence (docker datasource with orderable versioning or a tag probe in validate).

    Fingerprint: 724bd4aa6004147f79b334218538acaaf23ba7d7e3746ad50f8c91ccecca0c37

    filed by Hive review backlog
14. jeefy

    closed this as completedin #571on Oct 30, 2026
15. hivecommons-hive

    removed

    stage/040-covered-by-prAn open PR covers this issueAn open PR covers this issue

    on Oct 30, 2026