This is a fork of a third-party repo, so left untouched for now — but flagging so it's not a surprise when CI starts failing.
What's outdated
actions/checkout@v3 (both build-examples-master.yml and build-examples-pr.yml) — current major is v7.actions/setup-python@v4 (both workflows) — current major is v7.octokit/request-action@91508edec0a9561c2fefb9282491ced243bed312 (build-examples-pr.yml, remove-label job) — this SHA is from 2021 and the action.yml at that commit declares using: "node12". Node 12 support was removed from GitHub Actions runners years ago; GitHub may already be silently force-upgrading this, or it may start failing outright.
Why the octokit bump isn't a drop-in
The current release, v3.0.0, uses node24 — good — but it also changed the route templating syntax. The workflow currently uses old-style colon placeholders:
route: DELETE /repos/:repository/issues/:issue_number/labels/:name
Octokit v3 moved to brace-style templates ({owner}/{repo} etc.), so this with: block needs to be rewritten to match, not just have its version bumped. Untested rewrite, needs verification against the actual remove-label job behavior (removing the "CI: Build Examples" label after a labeled-PR build run).
When to act
Do this when CI actually starts failing (or when this fork gets handed back upstream and picked up again) — not urgent today.
See also esp32_idf5_https_server_compat#5 (same checkout/setup-python problem there).
— Claude Code (Claude Sonnet 5)
This is a fork of a third-party repo, so left untouched for now — but flagging so it's not a surprise when CI starts failing.
What's outdated
actions/checkout@v3(bothbuild-examples-master.ymlandbuild-examples-pr.yml) — current major isv7.actions/setup-python@v4(both workflows) — current major isv7.octokit/request-action@91508edec0a9561c2fefb9282491ced243bed312(build-examples-pr.yml,remove-labeljob) — this SHA is from 2021 and the action.yml at that commit declaresusing: "node12". Node 12 support was removed from GitHub Actions runners years ago; GitHub may already be silently force-upgrading this, or it may start failing outright.Why the octokit bump isn't a drop-in
The current release,
v3.0.0, usesnode24— good — but it also changed the route templating syntax. The workflow currently uses old-style colon placeholders:Octokit v3 moved to brace-style templates (
{owner}/{repo}etc.), so thiswith:block needs to be rewritten to match, not just have its version bumped. Untested rewrite, needs verification against the actualremove-labeljob behavior (removing the "CI: Build Examples" label after a labeled-PR build run).When to act
Do this when CI actually starts failing (or when this fork gets handed back upstream and picked up again) — not urgent today.
See also esp32_idf5_https_server_compat#5 (same checkout/setup-python problem there).
— Claude Code (Claude Sonnet 5)