Skip to content

chore(claude-lanes): re-pin callers to ci-workflows v0.58.0 - #833

Closed
melodic-claude-lanes-repin[bot] wants to merge 1 commit into
mainfrom
chore/repin-claude-lanes
Closed

melodic-claude-lanes-repin[bot] wants to merge 1 commit into
mainfrom
chore/repin-claude-lanes

Conversation

@melodic-claude-lanes-repin

Copy link
Copy Markdown
Contributor

No related issue: automated re-pin to the newest ci-workflows release

Summary

Re-pins every melodic-software/ci-workflows reference under
components/claude-lanes/ and components/claude-lanes-hosted/,
the managed-files-guard caller components, and this repository's own sync-family callers from
v0.55.0
to v0.58.0
(5e18f3d6cebd6fa5e66b0941ee0f7ed6ba288d6c), the newest ci-workflows
release. Opened by .github/workflows/maintenance-repin-ci-workflows.yml.

Fix

Same major version as the pin it replaces (v0.55.0 to v0.58.0).

Warning

Runner-policy lockstep requires a human. melodic-software/ci-workflows/.github/workflows/pr-review.yml melodic-software/ci-workflows/.github/workflows/pr-review.yml credentialReferences changed between revisions (from 3a2c748); melodic-software/ci-workflows/.github/workflows/pr-review-security.yml melodic-software/ci-workflows/.github/workflows/pr-review-security.yml credentialReferences changed between revisions (from 3a2c748). Before merging, register one approvedReusableWorkflowContracts entry for each declined workflow named above, add the rollout record in components/runner-policy/README.md, and add REPINE_LANE_SHA_V0_58_0 plus a verbatim copy-forward assertion in components/runner-policy/runner-policy.test.mjs (same shape as the v0.25.0 registration, PR #589). These surfaces were unchanged and were not copy-forwarded, because any decline suppresses every write: melodic-software/ci-workflows/.github/workflows/maintenance-sync-standards.yml. Register one approvedReusableWorkflowContracts entry for each of those withheld paths too. This pull request is never auto-merged.

Merging this cascades: maintenance-sync-standards.yml re-materializes the callers
into every target distribution/sync-manifest.yml marks a lane
caller (fleet or hosted) or a managed-files-guard caller
managed for, as a reviewed pull
request per target. This pull request is never auto-merged.

Verification

  • pin-comment-convention covers components/claude-lanes/*.yml
    and validates the rewritten pin comments' form.
  • claude-lanes component tests materialize and lint the callers.
  • runner-policy lints and tests pass when lockstep applied
    (policy-lockstep=manual).
  • Post-merge: the per-target sync pull requests are the real
    acceptance signal.

Related

Co-Authored-By: claude-lanes-repin <noreply@github.com>
@kyle-sexton

Copy link
Copy Markdown
Member

Superseded by #842 (ci-workflows v0.60.0).

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant