Skip to content

chore(ci): bump github actions to node 24 - #39

Merged
zepeng811 merged 1 commit into
circlefin:masterfrom
shanesavoie:chore/node24-action-bumps
Jun 18, 2026
Merged

zepeng811 merged 1 commit into
circlefin:masterfrom
shanesavoie:chore/node24-action-bumps

Conversation

@shanesavoie

Copy link
Copy Markdown
Contributor

Summary

SHA-pin update of every third-party GitHub Action used in this repo's shared workflows to its first Node-24-compatible release. Pre-emptive migration ahead of GitHub Actions runner Node 20 removal in Fall 2026.

Because this is the shared-workflows repo, downstream consumers (every repo that calls circlefin/circle-public-github-workflows/.github/workflows/<X>@v1) will pick up the new pins automatically when the v1 floating tag advances after merge.

Actions bumped (5 unique, 16 pins)

Action Old tag New SHA → tag
actions/checkout v4 df4cb1c0… (v6.0.3)
actions/download-artifact v4.3.0 3e5f45b2… (v8.0.1)
actions/github-script v7.1.0 3a2844b7… (v9.0.0)
actions/setup-node v4.x 48b55a01… (v6.4.0)
crazy-max/ghaction-import-gpg v6.x 2dc316de… (v7.0.0)

Files touched (4)

  • .github/workflows/actions-lint.yaml (2 pins)
  • .github/workflows/attach-release-assets.yaml (3 pins)
  • .github/workflows/conventional-commit-release.yaml (8 pins)
  • .github/workflows/pr-scan.yaml (3 pins)

Verification

Every emitted SHA was verified via gh api /repos/<owner>/<repo>/commits/<sha> before commit.

Test coverage

Three of the four modified workflows are self-exercised by this PR's own CI via the existing pipeline orchestrator (circle-public-workflows-pipeline.yaml):

Workflow How it's exercised on PR
actions-lint.yaml The lint-actions job in the pipeline calls it on every PR. If actions/checkout@v6.0.3 regresses, this job fails.
pr-scan.yaml The pr-scan job in the pipeline calls it on every PR. Exercises actions/checkout + actions/github-script bumps end-to-end.
conventional-commit-release.yaml The conventional-commit-release job in the pipeline calls it on every PR. Internal release-creation steps are gated on push so nothing is actually published — but the action-resolution + checkout + setup-node + github-script paths all execute.

Declared exception

  • attach-release-assets.yaml — the workflow's release_attach_assets job is hardcoded with if: github.event_name == 'push' && format('refs/heads/{0}', github.event.repository.default_branch) == github.ref. On a PR event, the whole job is skipped. Adding a synthetic test job would require modifying the workflow's gating logic to accept a test-mode override input — invasive for a pure SHA-bump change. The 3 pins in this file (actions/download-artifact@v8.0.1 and 2× actions/github-script@v9.0.0) will be exercised on the next release-cutting merge to master after this PR lands.

Background

Node 20 is being removed from GitHub Actions runners in Fall 2026 (see GitHub changelog). This PR pre-emptively bumps every pinned third-party action to its first Node-24-compatible release so the workflows keep running on the new runner default and downstream consumers stop seeing the deprecation warning bank in their job logs.

Bumps every pinned third-party action to its first Node-24-compatible
release. Affects 4 workflow files (16 pins total):

- .github/workflows/actions-lint.yaml          (2 pins)
- .github/workflows/attach-release-assets.yaml (3 pins)
- .github/workflows/conventional-commit-release.yaml (8 pins)
- .github/workflows/pr-scan.yaml               (3 pins)

Actions bumped (5 unique):
- actions/checkout            v4 -> v6.0.3
- actions/download-artifact   v4.3.0 -> v8.0.1
- actions/github-script       v7.1.0 -> v9.0.0
- actions/setup-node          v4.x -> v6.4.0
- crazy-max/ghaction-import-gpg v6.x -> v7.0.0

Every emitted SHA was verified via `gh api /repos/<owner>/<repo>/commits/<sha>`
before commit.
@zepeng811 zepeng811 changed the title chore(ci): bump GitHub Actions to Node 24 chore(ci): bump github actions to node 24 Jun 18, 2026
@zepeng811
zepeng811 merged commit ba33189 into circlefin:master Jun 18, 2026
9 of 11 checks passed
nexx88 pushed a commit that referenced this pull request Jul 1, 2026
🤖 I have created a release *beep* *boop*
---


##
[1.3.7](v1.3.6...v1.3.7)
(2026-06-18)


### Miscellaneous Chores

* **ci:** bump github actions to node 24
([#39](#39))
([ba33189](ba33189))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
zepeng811 pushed a commit that referenced this pull request Nov 12, 2026
## Summary

This repository holds 4 reusable workflows. Only `pr-scan.yaml` lets the
caller select a runner. The other 3 hardcode `runs-on: ubuntu-latest`.

This PR adds a `runs-on` input to those 3 workflows:

| Workflow | Job | Before | After |
| --- | --- | --- | --- |
| `attach-release-assets.yaml` | `release_attach_assets` |
`ubuntu-latest` | `${{ inputs.runs-on }}` |
| `actions-lint.yaml` | `lint_validate_actions` | `ubuntu-latest` | `${{
inputs.runs-on }}` |
| `conventional-commit-release.yaml` | `commit-lint` | `ubuntu-latest` |
`${{ inputs.runs-on }}` |
| `conventional-commit-release.yaml` | `release` | `ubuntu-latest` |
`${{ inputs.runs-on }}` |

Each new input copies the `runs-on` input that `pr-scan.yaml` already
defines. The description text, `required: false`, `type: string` and the
`ubuntu-latest` default all match that input.
`conventional-commit-release.yaml` applies one input to both of its
jobs.

`pr-scan.yaml` keeps its current content. This PR does not change it.

The default keeps the current behaviour, so no existing caller changes.

## Why this change is needed

A GitHub organization can enforce a runner policy. Such a policy can
forbid the GitHub-hosted `ubuntu-*` labels and allow only approved
runners. The policy then cancels any run that uses a forbidden label.

A policy of that kind reads every job in the caller workflow file. It
also reads the jobs of each reusable workflow that the caller starts. It
reads a job even when an `if` condition skips that job.

A hardcoded `runs-on` therefore breaks the caller in two ways:

1. The caller cannot select an approved runner for the reusable
workflow.
2. The caller loses its whole run, even when the affected job never
starts.

Point 2 is the harder one. A caller that starts
`attach-release-assets.yaml` only on a push to the default branch still
loses its pull request runs, because the policy reads the skipped job
too.

The same risk applies to `actions-lint.yaml` and
`conventional-commit-release.yaml`. This PR covers all 3 workflows
together, so no gap remains.

A caller-supplied `runs-on` also helps anyone who wants a larger runner
or a self-hosted runner for these workflows.

## Decision: this PR keeps the harden-runner step

PR #38 removes the `step-security/harden-runner` step and the `id-token:
write` permission from these workflows. That removal assumes the job
always runs on a custom runner that carries a built-in security agent.

That assumption holds only while `runs-on` stays hardcoded to such a
runner. Once `runs-on` becomes a caller input, the workflow cannot know
what the caller passes. A caller that passes `ubuntu-latest` would then
run with no runner-level agent and no workflow-level harden-runner.

I considered an `if:` condition that starts harden-runner only on a
runner without a built-in agent. I rejected that option for three
reasons:

1. The condition must match runner labels as strings. A caller may pass
a label, a runner group name, or a JSON array. A string match is
unreliable.
2. The condition must hold a list of approved labels. That list changes
over time, and this repository is public.
3. A fork of this repository has a different label set. The condition
gives the wrong result there.

This PR therefore keeps harden-runner for every runner.

Please confirm one point: the harden-runner action must support a runner
that already carries a security agent. I did not test that combination.

## Relationship to PR #38

I opened a separate PR instead of a rebase of #38. PR #38 changes the
same 4 files. Reasons:

- #38 is in a CONFLICTING state.
- The SHA pinning part of #38 is already on `master`. PR #39 and PR #41
pinned the actions to commit SHAs with version comments.
- The remaining content of #38 hardcodes one specific runner label and
removes harden-runner. This PR argues against both.
- A rebase of #38 must replace almost all of its content.

I excluded the SHA pinning from this PR, because `master` already has
it.

I did not close #38. Please decide what to do with it. I recommend that
you close it in favour of this PR.

## Open question for the repo owner: which default?

This PR uses `ubuntu-latest` as the default for all 3 inputs. That value
keeps the current behaviour and matches `pr-scan.yaml`. Please confirm
that choice or change it.

The trade-off:

- `ubuntu-latest` works for every consumer. Each consumer that needs
another runner must then pass one.
- A specific organization label is convenient for that one organization.
A consumer outside it cannot resolve the label. GitHub does not fail on
an unresolved label. The job queues until it times out.

This repository is public and has 14 forks. I could not determine if a
real external consumer exists. That answer decides the default.

## Required follow-up: the `v1` tag

A merge of this PR does not reach any consumer. Consumers use `@v1`.

The `v1` tag points to `057a20a7d108daaad3dc5e8e119cc2d53e42207c`, which
is release v1.3.5. The tags `v1`, `v1.3` and `stable` all still point to
that commit. `master` is 7 commits ahead, up to release v1.3.8.

The automatic tag move failed. The "Create additional tags" step of run
28533433898 failed with this error:

```
HttpError: Resource not accessible by integration - https://docs.github.com/rest/git/refs#create-a-reference
```

The release token appears to lack permission to write a git reference.

Two actions remain outside the scope of this PR:

1. Someone must repair the token permission for the "Create additional
tags" step.
2. Someone must move `v1`, `v1.3` and `stable` to a commit that contains
this change.

The `stable` tag matters too. The "Checkout Configs" step of
`pr-scan.yaml` checks out this repository at `ref: stable`.

I move no tag in this PR. Please tell me who owns that step.

## Testing

- I parsed all 5 workflow files with a YAML parser. Every file is valid.
- I confirmed that no job in `.github/workflows/` still hardcodes a
runner label.
- The pipeline of this repository calls the reusable workflows with no
`runs-on` value. The default keeps those calls working.
- This change does not touch PR #44 or PR #45. Those PRs change the
asset compile step of `attach-release-assets.yaml`.
- I opened this PR from a fork, because I have no write access. GitHub
therefore needs a maintainer to approve the workflow runs.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
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.

2 participants