Skip to content

agent-ingress pr-review job pins the legacy bare pr-review/stable (DEFECTIVE PIN): move both pin lines to pr-review/v1-stable #520

Closed

Description

@don-petry

Problem

The pr-review job in .github/workflows/agent-ingress.yml pins the legacy bare channel:

uses: petry-projects/.github-private/.github/workflows/pr-review.yml@pr-review/stable  # … DEFECTIVE PIN — see §5
  agent_ref: pr-review/stable

Release promotion moves only the major-scoped pr-review/v1-* channels, so no promoted pr-review release reaches markets. The bare tag moves only when someone moves it by hand.

The other five fleet callers are being migrated by a stub template in combsmith/.github#1125. That template cannot reach markets, because after the ADR-0007 collapse the pin lives inside an ingress job, not in a pr-review.yml stub file.

Change

Pin-only, two lines in the pr-review job of .github/workflows/agent-ingress.yml:

  • uses: …/pr-review.yml@pr-review/v1-stable
  • agent_ref: pr-review/v1-stable

Remove the # DEFECTIVE PIN — see §5 marker from that uses: line and keep the # NOSONAR(githubactions:S7637) first-party channel ref marker.

On 2026-10-10 pr-review/stable and pr-review/v1-stable both resolve to commit f6f2e384 on petry-projects/.github-private, so this changes no build.

Acceptance criteria

  1. Both lines in the pr-review job pin pr-review/v1-stable, in lockstep, and the DEFECTIVE PIN marker is gone from that line.
  2. Nothing else in agent-ingress.yml changes. In particular, leave the job's if: filter and its job-level concurrency: block alone (they are ADR-0007 / ADR-0010 decisions), and leave the ci-failure-analyst pin alone (tracked in markets ingress pins ci-failure-analyst by bare commit SHA (DEFECTIVE PIN): move it to a channel once stable is no longer frozen .github-private#2176).
  3. The PR description records the commit that pr-review/stable and pr-review/v1-stable each resolve to at implementation time. pr-review/stable is an annotated tag, so dereference it. If they differ, stop and report instead of changing the pin.
  4. Any doc in this repo that lists this pin as defective (the ingress collapse package, §5) is updated to match.

Activity

  1. don-petry commented on Oct 10, 2026

    @don-petry
    ContributorAuthor

    Dev-Lead Implementation Plan

    Issue: #520 — agent-ingress pr-review job pins the legacy bare pr-review/stable (DEFECTIVE PIN): move both pin lines to pr-review/v1-stable

    Scope

    Repin the pr-review job in .github/workflows/agent-ingress.yml (uses: + agent_ref:) from pr-review/stable to pr-review/v1-stable in lockstep, and drop the DEFECTIVE PIN marker on that line.

    Pre-check (2026-10-10, git ls-remote petry-projects/.github-private): pr-review/stable → f6f2e384d6bf2f360acaf44eef0324632368394f (no ^{} peel entry was returned, so the ref resolves directly to this commit), pr-review/v1-stable → f6f2e384d6bf2f360acaf44eef0324632368394f. Identical, so I'll go ahead.

    Implementation Checklist

    • .github/workflows/agent-ingress.yml: change the two pin lines and remove the # DEFECTIVE PIN — see §5 marker (keep the NOSONAR marker)
    • Docs: the ingress collapse package (docs/initiatives/agent-ingress-collapse-markets.md) isn't in this repo, so there's no in-repo §5 doc to update

    Tests to Write

    • .github/scripts/tests/agent-ingress-workflow.bats: update the pin-parity assertions to expect pr-review/v1-stable, and assert the DEFECTIVE PIN marker is gone from the pr-review uses: line

    Test Command

    bats .github/scripts/tests/agent-ingress-workflow.bats

  2. don-petry commented on Oct 10, 2026

    @don-petry
    ContributorAuthor

    Dev-Lead: Progress (in progress — not yet durable)

    Provisional. Nothing is pushed yet. The automation posts the authoritative completion record (with PR number + head SHA) after the push. Read the notes below as intent, not delivered results.

    Plan Execution (intended)

    • Repinned the pr-review job's uses: and with.agent_ref from pr-review/stable to pr-review/v1-stable together. Removed the # DEFECTIVE PIN — see §5 marker and kept the # NOSONAR(githubactions:S7637) first-party channel ref marker.
    • No other part of agent-ingress.yml was touched: the if: filter, job-level concurrency: and ci-failure-analyst pin are unchanged.

    Pin resolution at implementation time (for the PR description, AC #3)

    git ls-remote https://github.com/petry-projects/.github-private.git on 2026-10-10:

    • pr-review/stable → f6f2e384d6bf2f360acaf44eef0324632368394f (no ^{} peeled entry was returned, so the tag ref resolves directly to this commit)
    • pr-review/v1-stable → f6f2e384d6bf2f360acaf44eef0324632368394f

    Same commit, so no build changes.

    Files touched (this workspace, not yet pushed)

    • .github/workflows/agent-ingress.yml: the two pin lines, plus the marker removal
    • .github/scripts/tests/agent-ingress-workflow.bats: the pin-parity test now expects pr-review/v1-stable. A new guard test checks that the pr-review uses: line pins @pr-review/v1-stable, keeps the NOSONAR marker and has no DEFECTIVE PIN marker. Both failed before the workflow edit.

    Notes

    • AC fix: remove gradle ecosystem from Dependabot config #4: the collapse package with §5 (docs/initiatives/agent-ingress-collapse-markets.md) lives in petry-projects/.github-private, not in this repo, so nothing in this repo needed updating. The §5 entry over there needs a separate follow-up.
    • .dev-lead/scripts/lib/ci-status.sh has a historical comment mentioning pr-review/stable. It's synced dev-lead tooling and doesn't describe this pin as defective, so I left it alone.
  3. don-petry commented on Oct 10, 2026

    @don-petry
    ContributorAuthor

    Dev-Lead: Implementation Complete — PR #521

    The implementation for issue #520 is durable: commits are pushed and a pull request is open. This record is backed by verifiable artifacts you can confirm in one click.

    Review happens on the PR. Acceptance criteria and test results are evidenced by the PR's diff and CI checks — not asserted here. If a later stage fails, this claim is retracted in place.

  4. added a commit that references this issue on Oct 10, 2026
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

    bugBug reportsdev-leadFor dev-lead agent pickup

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions