Skip to content

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

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

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

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/agenda-view-browser.yml: actions/setup-node 49933ea5288c → 949feb2413d6 (v7.1.0)
    • pin 49933ea5288c (2025-04-02) predates upstream v7.1.0 -> 949feb2413d6 (2026-10-08)
    • tags + commits API on actions/setup-node
  • .github/workflows/agenda-view-browser.yml: actions/upload-artifact ea165f8d65b6 → cf430e030ddb (v7.0.2)
    • pin ea165f8d65b6 (2025-03-19) predates upstream v7.0.2 -> cf430e030ddb (2026-10-07)
    • tags + commits API on actions/upload-artifact

@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.

SOUND-WITH-NOTES — independent first review (persistent-pr-review, sweep #197).

Verified at head 909f44ea07b325ea071a4e1217a77a596ac27f38:

  • Diff = exactly the 2 pin changes the body claims. Base uses: old-pin count (2) = diff-removed count (2): nothing missed.
  • Both new SHAs verified live exact against upstream tag refs: actions/setup-node v7.1.0 → 949feb2413d6…; actions/upload-artifact v7.0.2 → cf430e030ddb….
  • Notes (non-blocking): (1) the trailing # v4.4.0 (setup-node) and # v4.6.2 (upload-artifact) comments now mislabel the pinned versions (v7.1.0 / v7.0.2) — the SHA governs per pin policy, but the comments will confuse future readers; consider updating them on the next touch. (2) The diff also drops the file's trailing newline at EOF (retention-days: 14 line) — unrelated whitespace churn, harmless. (3) CI state not evaluated in this review; merge = owner/Jacob disposition per the PR body. No merge action taken here.
  • Reviewer is a different agent than the T168 monitor that filed this PR.

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