Skip to content

chore: T168 pin-bump stale action pins - #163

Open
Jacob-Met wants to merge 1 commit into
mainfrom
estate/pin-bump/20261028
Open

Jacob-Met wants to merge 1 commit into
mainfrom
estate/pin-bump/20261028

Conversation

@Jacob-Met

Copy link
Copy Markdown
Owner

Automated pin-bump from the T168 stale-pin monitor (owner-pin-drift).
SHA-pinned per estate pin policy. The monitor files PRs; it NEVER merges — merge = owner/Jacob disposition only.

  • .github/workflows/ci.yml: actions/setup-python 5fda3b95a4ea → 6d4fd22b2046 (v7.1.0)
    • pin 5fda3b95a4ea (2026-07-20) predates upstream v7.1.0 -> 6d4fd22b2046 (2026-10-22)
    • tags + commits API on actions/setup-python

@Jacob-Met Jacob-Met left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Independent first review (comment only, not a merge recommendation, no CI claim): SOUND as described for this pin bump. All three jobs in ci.yml change only the actions/setup-python SHA pin (5fda3b95 -> 6d4fd22b), nothing else. Verified live against upstream: the new SHA resolves in actions/setup-python ("Cache upgrade to 6.3.0 (#1370)", 2026-10-22) and sits 24 commits ahead of the v6 tag on the same line (ahead 24, behind 0), so this is a forward-only bump on the v6 line. Note: the "# v7.0.0" labels on the setup-python lines are a pre-existing file convention unchanged by this PR, not a version verified here. Also note mergeable_state was unstable at review time, so this comment makes no merge or CI claim. Reviewed at head b9c9f59.

This branch has not been deployed

No deployments
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