Skip to content

CI: bump github actions to recent versions#96

Open
hauke wants to merge 5 commits intoopenwrt:mainfrom
hauke:action-update
Open

CI: bump github actions to recent versions#96
hauke wants to merge 5 commits intoopenwrt:mainfrom
hauke:action-update

Conversation

@hauke
Copy link
Copy Markdown
Member

@hauke hauke commented Apr 12, 2026

  • CI: Bump actions/upload-artifact from 6 to 7

    v7 adds support for direct (unzipped) single-file uploads via a new
    archive: false parameter and migrates the package to ESM internally.
    Both changes are transparent to existing usage — no inputs, outputs, or
    behaviour of the action change for callers that do not use the new
    parameter.

    Release notes: https://github.com/actions/upload-artifact/releases/tag/v7.0.0

  • CI: Bump actions/download-artifact from 7 to 8

    v8 migrates the package to ESM and adds support for direct (unzipped)
    downloads to match the new upload-artifact direct upload feature.

    One behaviour change: hash mismatches now error by default instead of
    logging a warning. This is safe for correct workflows where artifact
    content does not change between upload and download.

    Release notes: https://github.com/actions/download-artifact/releases/tag/v8.0.0

  • CI: Bump actions/github-script from 8 to 9

    v9 upgrades to @actions/github v9 (ESM-only) and adds a getOctokit
    factory function directly to the script context.

    Breaking change: require('@actions/github') no longer works in inline
    scripts. The only usage here passes github and context as parameters to
    a local CommonJS module (process_formalities.js) which does not import
    @actions/github itself, so the upgrade is safe.

    Release notes: https://github.com/actions/github-script/releases/tag/v9.0.0

  • CI: Bump docker/login-action from 3 to 4 and docker/build-push-action from 6 to 7

    Both actions update their runtime to Node 24 (requires Actions Runner
    v2.327.1+) and migrate to ESM internally. No changes to inputs, outputs,
    or behaviour for existing callers.

    docker/build-push-action v7 additionally removes two deprecated
    environment variables (DOCKER_BUILD_NO_SUMMARY,
    DOCKER_BUILD_EXPORT_RETENTION_DAYS) which are not used in these
    workflows.

    Release notes:

  • CI: Bump octokit/request-action from 2.x to 3

    v3 updates the runtime to Node 24 (requires Actions Runner v2.327.1+)
    and switches the build from NCC to ESBuild. No changes to inputs,
    outputs, or behaviour for callers.

    Release notes: https://github.com/octokit/request-action/releases/tag/v3.0.0

hauke and others added 5 commits April 12, 2026 23:22
v7 adds support for direct (unzipped) single-file uploads via a new
`archive: false` parameter and migrates the package to ESM internally.
Both changes are transparent to existing usage — no inputs, outputs, or
behaviour of the action change for callers that do not use the new
parameter.

Release notes: https://github.com/actions/upload-artifact/releases/tag/v7.0.0

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
v8 migrates the package to ESM and adds support for direct (unzipped)
downloads to match the new upload-artifact direct upload feature.

One behaviour change: hash mismatches now error by default instead of
logging a warning. This is safe for correct workflows where artifact
content does not change between upload and download.

Release notes: https://github.com/actions/download-artifact/releases/tag/v8.0.0

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
v9 upgrades to @actions/github v9 (ESM-only) and adds a getOctokit
factory function directly to the script context.

Breaking change: require('@actions/github') no longer works in inline
scripts. The only usage here passes github and context as parameters to
a local CommonJS module (process_formalities.js) which does not import
@actions/github itself, so the upgrade is safe.

Release notes: https://github.com/actions/github-script/releases/tag/v9.0.0

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
… from 6 to 7

Both actions update their runtime to Node 24 (requires Actions Runner
v2.327.1+) and migrate to ESM internally. No changes to inputs, outputs,
or behaviour for existing callers.

docker/build-push-action v7 additionally removes two deprecated
environment variables (DOCKER_BUILD_NO_SUMMARY,
DOCKER_BUILD_EXPORT_RETENTION_DAYS) which are not used in these
workflows.

Release notes:
- https://github.com/docker/login-action/releases/tag/v4.0.0
- https://github.com/docker/build-push-action/releases/tag/v7.0.0

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
v3 updates the runtime to Node 24 (requires Actions Runner v2.327.1+)
and switches the build from NCC to ESBuild. No changes to inputs,
outputs, or behaviour for callers.

Release notes: https://github.com/octokit/request-action/releases/tag/v3.0.0

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
@github-actions
Copy link
Copy Markdown

Warning

Some formality checks failed.

Consider (re)reading submissions guidelines.

Failed checks

Issues marked with an ❌ are failing checks.

Commit d4d581a

  • ❌ First word after prefix in subject should not be capitalized

Commit 69d407d

  • ❌ First word after prefix in subject should not be capitalized
  • ❌ Commit subject length: recommended max 60, required max 80 characters

Commit 2eefc9e

  • ❌ First word after prefix in subject should not be capitalized

Commit a51cfa2

  • ❌ First word after prefix in subject should not be capitalized

Commit 3e1624a

  • ❌ First word after prefix in subject should not be capitalized

For more details, see the full job log.

Something broken? Consider providing feedback.

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