Skip to content

Update GitHub actions (major)#257

Open
renovate[bot] wants to merge 1 commit into
2/edgefrom
renovate/major-github-actions
Open

Update GitHub actions (major)#257
renovate[bot] wants to merge 1 commit into
2/edgefrom
renovate/major-github-actions

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented May 5, 2026

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Type Update Change
actions/checkout action major v5v6
actions/checkout action major v4v6
actions/download-artifact action major v4v8
actions/upload-artifact action major v4v7
canonical/data-platform-workflows action major v32.1.0v49.0.2
ubuntu github-runner major 22.0424.04

Release Notes

actions/checkout (actions/checkout)

v6.0.2

Compare Source

v6.0.1

Compare Source

v6.0.0

Compare Source

v6

Compare Source

v5.0.1

Compare Source

What's Changed

Full Changelog: actions/checkout@v5...v5.0.1

actions/download-artifact (actions/download-artifact)

v8.0.1

Compare Source

What's Changed

Full Changelog: actions/download-artifact@v8...v8.0.1

v8.0.0

Compare Source

v8 - What's new
Direct downloads

To support direct uploads in actions/upload-artifact, the action will no longer attempt to unzip all downloaded files. Instead, the action checks the Content-Type header ahead of unzipping and skips non-zipped files. Callers wishing to download a zipped file as-is can also set the new skip-decompress parameter to false.

Enforced checks (breaking)

A previous release introduced digest checks on the download. If a download hash didn't match the expected hash from the server, the action would log a warning. Callers can now configure the behavior on mismatch with the digest-mismatch parameter. To be secure by default, we are now defaulting the behavior to error which will fail the workflow run.

ESM

To support new versions of the @​actions/* packages, we've upgraded the package to ESM.

What's Changed

Full Changelog: actions/download-artifact@v7...v8.0.0

v8

Compare Source

v7.0.0

Compare Source

v7 - What's new

[!IMPORTANT]
actions/download-artifact@​v7 now runs on Node.js 24 (runs.using: node24) and requires a minimum Actions Runner version of 2.327.1. If you are using self-hosted runners, ensure they are updated before upgrading.

Node.js 24

This release updates the runtime to Node.js 24. v6 had preliminary support for Node 24, however this action was by default still running on Node.js 20. Now this action by default will run on Node.js 24.

What's Changed
New Contributors

Full Changelog: actions/download-artifact@v6.0.0...v7.0.0

v7

Compare Source

v6.0.0

Compare Source

What's Changed

BREAKING CHANGE: this update supports Node v24.x. This is not a breaking change per-se but we're treating it as such.

New Contributors

Full Changelog: actions/download-artifact@v5...v6.0.0

v6

Compare Source

v5.0.0

Compare Source

What's Changed

v5.0.0

🚨 Breaking Change

This release fixes an inconsistency in path behavior for single artifact downloads by ID. If you're downloading single artifacts by ID, the output path may change.

What Changed

Previously, single artifact downloads behaved differently depending on how you specified the artifact:

  • By name: name: my-artifact → extracted to path/ (direct)
  • By ID: artifact-ids: 12345 → extracted to path/my-artifact/ (nested)

Now both methods are consistent:

  • By name: name: my-artifact → extracted to path/ (unchanged)
  • By ID: artifact-ids: 12345 → extracted to path/ (fixed - now direct)
Migration Guide
✅ No Action Needed If:
  • You download artifacts by name
  • You download multiple artifacts by ID
  • You already use merge-multiple: true as a workaround
⚠️ Action Required If:

You download single artifacts by ID and your workflows expect the nested directory structure.

Before v5 (nested structure):

- uses: actions/download-artifact@v4
  with:
    artifact-ids: 12345
    path: dist

### Files were in: dist/my-artifact/

Where my-artifact is the name of the artifact you previously uploaded

To maintain old behavior (if needed):

- uses: actions/download-artifact@v5
  with:
    artifact-ids: 12345
    path: dist/my-artifact  # Explicitly specify the nested path

New Contributors

Full Changelog: actions/download-artifact@v4...v5.0.0

v5

Compare Source

v4.3.0

Compare Source

What's Changed

New Contributors

Full Changelog: actions/download-artifact@v4.2.1...v4.3.0

v4.2.1

Compare Source

What's Changed

Full Changelog: actions/download-artifact@v4.2.0...v4.2.1

v4.2.0

Compare Source

What's Changed

New Contributors

Full Changelog: actions/download-artifact@v4.1.9...v4.2.0

v4.1.9

Compare Source

What's Changed

New Contributors

Full Changelog: actions/download-artifact@v4.1.8...v4.1.9

v4.1.8

Compare Source

What's Changed

Full Changelog: actions/download-artifact@v4.1.7...v4.1.8

v4.1.7

Compare Source

What's Changed

Full Changelog: actions/download-artifact@v4.1.6...v4.1.7

v4.1.6

Compare Source

What's Changed

Full Changelog: actions/download-artifact@v4.1.5...v4.1.6

v4.1.5

Compare Source

What's Changed

  • Update readme with v3/v2/v1 deprecation notice by @​robherley in #​322
  • Update dependencies @actions/core to v1.10.1 and @actions/artifact to v2.1.5

Full Changelog: actions/download-artifact@v4.1.4...v4.1.5

v4.1.4

Compare Source

What's Changed

Full Changelog: actions/download-artifact@v4...v4.1.4

v4.1.3

Compare Source

What's Changed

New Contributors

Full Changelog: actions/download-artifact@v4...v4.1.3

v4.1.2

Compare Source

v4.1.1

Compare Source

  • Fix transient request timeouts #​249
  • Bump @actions/artifacts to latest version

v4.1.0

Compare Source

What's Changed

New Contributors

Full Changelog: actions/download-artifact@v4...v4.1.0

actions/upload-artifact (actions/upload-artifact)

v7.0.1

Compare Source

What's Changed

Full Changelog: actions/upload-artifact@v7...v7.0.1

v7.0.0

Compare Source

v7 What's new

Direct Uploads

Adds support for uploading single files directly (unzipped). Callers can set the new archive parameter to false to skip zipping the file during upload. Right now, we only support single files. The action will fail if the glob passed resolves to multiple files. The name parameter is also ignored with this setting. Instead, the name of the artifact will be the name of the uploaded file.

ESM

To support new versions of the @actions/* packages, we've upgraded the package to ESM.

What's Changed

New Contributors

Full Changelog: actions/upload-artifact@v6...v7.0.0

v7

Compare Source

v6.0.0

Compare Source

v6

Compare Source

v5.0.0

Compare Source

v5

Compare Source

v4.6.2

Compare Source

What's Changed

  • Update to use artifact 2.3.2 package & prepare for new upload-artifact release by @​salmanmkc in #​685

New Contributors

Full Changelog: actions/upload-artifact@v4...v4.6.2

v4.6.1

Compare Source

What's Changed

Full Changelog: actions/upload-artifact@v4...v4.6.1

v4.6.0

Compare Source

What's Changed

Full Changelog: actions/upload-artifact@v4...v4.6.0

v4.5.0

Compare Source

What's Changed

New Contributors

Full Changelog: actions/upload-artifact@v4.4.3...v4.5.0

v4.4.3

Compare Source

What's Changed

Full Changelog: actions/upload-artifact@v4.4.2...v4.4.3

v4.4.2

Compare Source

What's Changed

  • Bump @actions/artifact to 2.1.11 by @​robherley in #​627
    • Includes fix for relative symlinks not resolving properly

Full Changelog: actions/upload-artifact@v4.4.1...v4.4.2

v4.4.1

Compare Source

What's Changed

New Contributors

Full Changelog: actions/upload-artifact@v4.4.0...v4.4.1

v4.4.0

Compare Source

Notice: Breaking Changes ⚠️

We will no longer include hidden files and folders by default in the upload-artifact action of this version. This reduces the risk that credentials are accidentally uploaded into artifacts. Customers who need to continue to upload these files can use a new option, include-hidden-files, to continue to do so.

See "Notice of upcoming deprecations and breaking changes in GitHub Actions runners" changelog and this issue for more details.

What's Changed

Full Changelog: actions/upload-artifact@v4.3.6...v4.4.0

v4.3.6

Compare Source

What's Changed

Full Changelog: actions/upload-artifact@v4...v4.3.6

v4.3.5

Compare Source

What's Changed

Full Changelog: actions/upload-artifact@v4.3.4...v4.3.5

v4.3.4

Compare Source

What's Changed

Full Changelog: actions/upload-artifact@v4.3.3...v4.3.4

v4.3.3

Compare Source

What's Changed

Full Changelog: actions/upload-artifact@v4.3.2...v4.3.3

v4.3.2

Compare Source

What's Changed

New Contributors

Full Changelog: actions/upload-artifact@v4.3.1...v4.3.2

v4.3.1

Compare Source

v4.3.0

Compare Source

What's Changed

Full Changelog: actions/upload-artifact@v4...v4.3.0

v4.2.0

Compare Source

What's Changed

Full Changelog: actions/upload-artifact@v4...v4.2.0

v4.1.0

Compare Source

What's Changed

New Contributors

Full Changelog: actions/upload-artifact@v4...v4.1.0

canonical/data-platform-workflows (canonical/data-platform-workflows)

v49.0.2

Compare Source

What's Changed

Full Changelog: canonical/data-platform-workflows@v49.0.1...v49.0.2

v49.0.1

Compare Source

What's Changed
New Contributors

Full Changelog: canonical/data-platform-workflows@v49.0.0...v49.0.1

v49.0.0

Compare Source

What's Changed

Full Changelog: canonical/data-platform-workflows@v48.1.2...v49.0.0

v49

Compare Source

v48.1.2

Compare Source

What's Changed
New Contributors

Full Changelog: canonical/data-platform-workflows@v48.1.1...v48.1.2

v48.1.1

Compare Source

What's Changed

Full Changelog: canonical/data-platform-workflows@v48.1.0...v48.1.1

v48.1.0

Compare Source

What's Changed

Full Changelog: canonical/data-platform-workflows@v48.0.5...v48.1.0

v48.0.5

Compare Source

What's Changed

Full Changelog: canonical/data-platform-workflows@v48.0.4...v48.0.5

v48.0.4

Compare Source

What's Changed

New Contributors

Full Changelog: canonical/data-platform-workflows@v48.0.3...v48.0.4

v48.0.3

Compare Source

What's Changed

Full Changelog: canonical/data-platform-workflows@v48.0.2...v48.0.3

v48.0.2

Compare Source

What's Changed

Full Changelog: canonical/data-platform-workflows@v48.0.1...v48.0.2

v48.0.1

Compare Source

What's Changed

Full Changelog: canonical/data-platform-workflows@v48.0.0...v48.0.1

v48.0.0

Compare Source

What's Changed

Full Changelog: canonical/data-platform-workflows@v47.0.2...v48.0.0

Migration instructions for v48

Remove Snap Store secret and follow usage docs for release_snap_edge.yaml or release_snap_pr.yaml to create new environment secret

Combined migration instructions for v43-v48 (i.e. for migrating from v42 to v48)

All workflows

For each reusable workflow, check the usage docs (https://github.com/canonical/data-platform-workflows?tab=readme-ov-file#usage) and, for each workflow call, update permissions to match the usage docs

integration_test_charm.yaml

https://github.com/canonical/data-platform-workflows/blob/v29.1.0/.github/workflows/integration_test_charm_deprecation_notice.md#migration-instructions

lint.yaml
  • Replace lint.yaml with lint_workflows.yaml
  • Add .github/zizmor.yaml file following usage docs
  • Create a separate job (outside of reusable workflow call) to run tox run -e lint
release_snap.yaml

For releases to edge

  • Replace release_snap.yaml with release_snap_edge.yaml
  • Replace channel input with track input
    • Remove "/edge" from channel input value to get new track input value
  • Remove SNAP_STORE_TOKEN secret and follow usage docs to create new environment secret. Update secret name in workflow call.
  • Remove create-git-tags input

For releases of PR branches:

  • Replace release_snap.yaml with release_snap_pr.yaml
  • Replace channel input with track input
  • Remove SNAP_STORE_TOKEN secret and follow usage docs to create new environment secret. Update secret name in workflow call.
  • Remove create-git-tags input
release_rock.yaml
  • Replace release_rock.yaml with release_rock_edge.yaml
  • Remove create-git-tags input
_mirror_charm.yaml
  • Remove MIRROR_REPOS_PAT secret and follow usage docs to create new environment secret
_update_bundle.yaml
  • Remove CREATE_PR_APP_TOKEN secret and follow usage docs to create new environment secret
release_charm_pr.yaml
release_charm_edge.yaml and release_charm_pr.yaml

No further action needed at this time. Once candid auth is removed (https://discourse.canonical.com/t/charmhub-teams-deprecation/7035), we will have a breaking change for release_charm_*.yaml and new secrets will need to be created. (We are waiting for charmcraft to add support for non-candid auth.)

v48

Compare Source

v47.0.2

Compare Source

What's Changed

Full Changelog: canonical/data-platform-workflows@v47.0.1...v47.0.2

v47.0.1

Compare Source

What's Changed

Full Changelog: canonical/data-platform-workflows@v47.0.0...v47.0.1

v47.0.0

Compare Source

What's Changed

Full Changelog: canonical/data-platform-workflows@v46.0.0...v47.0.0

[!TIP]
Combined migration instructions for v43-v48 (i.e. from v42 to v48) are available at https://github.com/canonical/data-platform-workflows/releases/tag/v48.0.0

v47

Compare Source

v46.0.0

Compare Source

What's Changed

Full Changelog: canonical/data-platform-workflows@v45.0.0...v46.0.0

Migration instructions

[!TIP]
Combined migration instructions for v43-v48 (i.e. from v42 to v48) are available at https://github.com/canonical/data-platform-workflows/releases/tag/v48.0.0

  • Replace lint.yaml with lint_workflows.yaml
  • Add job to run tox run -e lint (or similar)

v46

Compare Source

v45.0.0

Compare Source

What's Changed

Full Changelog: canonical/data-platform-workflows@v44.0.2...v45.0.0

Migration instructions

[!TIP]
Combined migration instructions for v43-v48 (i.e. from v42 to v48) are available at https://github.com/canonical/data-platform-workflows/releases/tag/v48.0.0

release_snap.yaml

For releases to edge

  • Replace release_snap.yaml with release_snap_edge.yaml
  • Replace channel input with track input
    • Remove "/edge" from channel input value to get new track input value
  • Remove SNAP_STORE_TOKEN secret and follow usage docs to create new environment secret. Update secret name in workflow call.
  • Remove create-git-tags input

For releases of PR branches:

  • Replace release_snap.yaml with release_snap_pr.yaml
  • Replace channel input with track input
  • Remove SNAP_STORE_TOKEN secret and follow usage docs to create new environment secret. Update secret name in workflow call.
  • Remove create-git-tags input
release_rock.yaml
  • Replace release_rock.yaml with release_rock_edge.yaml
  • Remove create-git-tags input
_mirror_charm.yaml
  • Remove MIRROR_REPOS_PAT secret and follow usage docs to create new environment secret
_update_bundle.yaml
  • Remove CREATE_PR_APP_TOKEN secret and follow usage docs to create new environment secret
release_charm_pr.yaml

v45

Compare Source

v44.0.2

Compare Source

What's Changed

Full Changelog: canonical/data-platform-workflows@v44.0.1...v44.0.2

v44.0.1

Compare Source

What's Changed

Full Changelog: canonical/data-platform-workflows@v44.0.0...v44.0.1

v44.0.0

Compare Source

What's Changed

Full Changelog: canonical/data-platform-workflows@v43.0.0...v44.0.0

Migration instructions

[!TIP]
Combined migration instructions for v43-v48 (i.e. from v42 to v48) are available at https://github.com/canonical/data-platform-workflows/releases/tag/v48.0.0

For each reusable workflow, check the usage docs (https://github.com/canonical/data-platform-workflows?tab=readme-ov-file#usage) and, for each workflow call, update permissions to match the usage docs

v44

Compare Source

v43.0.0

Compare Source

What's Changed

Full Changelog: <https://github.com/canonical/data-platform-wo

Note

PR body was truncated to here.


Configuration

📅 Schedule: (in timezone Etc/UTC)

  • Branch creation
    • Between 01:00 AM and 07:59 AM, only on Tuesday (* 1-7 * * 2)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the not bug or enhancement PR is not 'bug' or 'enhancement'. For release notes label May 5, 2026
@renovate renovate Bot force-pushed the renovate/major-github-actions branch from 2b30c45 to 01094c2 Compare May 12, 2026 03:33
@renovate renovate Bot force-pushed the renovate/major-github-actions branch from 01094c2 to 806fa8a Compare May 19, 2026 03:42
@renovate renovate Bot force-pushed the renovate/major-github-actions branch from 806fa8a to 1413484 Compare June 2, 2026 03:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

not bug or enhancement PR is not 'bug' or 'enhancement'. For release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants