chore(deps): update github-actions to 3.14 - #2391
Conversation
Workflow source neededPR #2391 needs either a linked GitHub issue or one valid non-issue Workflow Source before PR metadata automation can manage it safely. Please do one of:
Once a valid source is present, this warning will not be reposted. |
Automated Status SummaryHead SHA: 7a0157a
Coverage Overview
Updated automatically; will refresh on subsequent CI/Docker completions. Keepalive checklistScopeNo scope information available Tasks
Acceptance criteria
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: fec9763316
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| uses: actions/setup-python@v6 | ||
| with: | ||
| python-version: '3.12' | ||
| python-version: '3.14' |
There was a problem hiding this comment.
Keep agent runners on supported Python
In the agent runner context, this fixed 3.14 is used before the workflow installs the checked-out repository's requirements*.txt and editable pyproject.toml (later in this job). I checked .github/workflows/pr-00-gate.yml, and the supported/default CI matrix remains primary-python-version: '3.12' with python-versions: '["3.12", "3.13"]', so repos whose dependencies or requires-python are valid for the current gate but not for 3.14 will now fail during setup before the agent can run. Keep these reusable runners on the supported runtime or make the Python version a caller input/read from the repo.
Useful? React with 👍 / 👎.
Health 74 "Check Template Drift" was RED on main: 7 of 15 allowlisted root->template workflow pairs had stale fingerprints, so they showed as unallowlisted drift (exit 1). They went stale after action-version bumps (#2391/#2394) and root feature work changed the normalized content of both sides without re-baselining. Each of the 7 was examined; all are intentional, bidirectional divergence rather than a missing consumer improvement: - consumer template workflows SHA-pin third-party actions per the fleet action-pin contract (docs/HISTORY.md, PR #1925) and carry LangSmith tracing env; - the root Workflows-repo copies use floating major tags plus repo-internal concurrency + sparse-checkout (docs/fixes/sparse-checkout-audit-2026-02-03.csv); - agents-63-issue-intake is additionally an alias-mapped Workflows-internal superset (~1.7k lines) vs the 216-line consumer intake template. Aligning the template to root would strip the contractually-required consumer action pins from all consumers, so the entries are re-baselined (fingerprints refreshed + documented reasons) rather than aligned. The 8 already-passing entries are untouched. Verified: scripts/check_template_drift.py --allowlist config/template-drift-allowlist.txt now reports 0 unallowlisted drift (15 allowlisted, 3 in sync), exit 0. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> # Conflicts: # config/template-drift-allowlist.txt
…2397) Health 74 "Check Template Drift" was RED on main: 7 of 15 allowlisted root->template workflow pairs had stale fingerprints, so they showed as unallowlisted drift (exit 1). They went stale after action-version bumps (#2391/#2394) and root feature work changed the normalized content of both sides without re-baselining. Each of the 7 was examined; all are intentional, bidirectional divergence rather than a missing consumer improvement: - consumer template workflows SHA-pin third-party actions per the fleet action-pin contract (docs/HISTORY.md, PR #1925) and carry LangSmith tracing env; - the root Workflows-repo copies use floating major tags plus repo-internal concurrency + sparse-checkout (docs/fixes/sparse-checkout-audit-2026-02-03.csv); - agents-63-issue-intake is additionally an alias-mapped Workflows-internal superset (~1.7k lines) vs the 216-line consumer intake template. Aligning the template to root would strip the contractually-required consumer action pins from all consumers, so the entries are re-baselined (fingerprints refreshed + documented reasons) rather than aligned. The 8 already-passing entries are untouched. Verified: scripts/check_template_drift.py --allowlist config/template-drift-allowlist.txt now reports 0 unallowlisted drift (15 allowlisted, 3 in sync), exit 0. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> # Conflicts: # config/template-drift-allowlist.txt Co-authored-by: Tim Stranske <tim@stranskemo.com>
This PR contains the following updates:
3.12→3.14Release Notes
actions/python-versions (python)
v3.14.6: 3.14.6Compare Source
Python 3.14.6
v3.14.5: 3.14.5Compare Source
Python 3.14.5
v3.14.4: 3.14.4Compare Source
Python 3.14.4
v3.14.3: 3.14.3Compare Source
Python 3.14.3
v3.14.2: 3.14.2Compare Source
Python 3.14.2
v3.14.1: 3.14.1Compare Source
Python 3.14.1
v3.14.0: 3.14.0Compare Source
Python 3.14.0
v3.13.14: 3.13.14Compare Source
Python 3.13.14
v3.13.13: 3.13.13Compare Source
Python 3.13.13
v3.13.12: 3.13.12Compare Source
Python 3.13.12
v3.13.11: 3.13.11Compare Source
Python 3.13.11
v3.13.10: 3.13.10Compare Source
Python 3.13.10
v3.13.9: 3.13.9Compare Source
Python 3.13.9
v3.13.8: 3.13.8Compare Source
Python 3.13.8
v3.13.7: 3.13.7Compare Source
Python 3.13.7
v3.13.6: 3.13.6Compare Source
Python 3.13.6
v3.13.5: 3.13.5Compare Source
Python 3.13.5
v3.13.4: 3.13.4Compare Source
Python 3.13.4
v3.13.3: 3.13.3Compare Source
Python 3.13.3
v3.13.2: 3.13.2Compare Source
Python 3.13.2
v3.13.1: 3.13.1Compare Source
Python 3.13.1
v3.13.0: 3.13.0Compare Source
Python 3.13.0
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.