github balena-io/open-balena v4.1.592

5 hours ago

Update dependency balena-io/balena-cli to v22.5.5

Notable changes

-actions/setup-python (actions/setup-python)
-actions/setup-node (actions/setup-node)

balena-io/balena-cli (balena-io/balena-cli)

v22.5.5

Compare Source

Update actions/setup-python action to v6
Notable changes
actions/setup-python (actions/setup-python)
v6

Compare Source

v5

Compare Source

List of commits

c366802 (Update actions/setup-python action to v6, 2025-11-14)

v22.5.4

Compare Source

7899f0a (renovate: Clean node_modules and npm cache before dedupe, 2025-11-14)

v22.5.3

Compare Source

Update actions/setup-node action to v6
Notable changes
actions/setup-node (actions/setup-node)
v6

Compare Source

v5

Compare Source

List of commits

9d82d2d (Update actions/setup-node action to v6, 2025-11-13)

v22.5.2

Compare Source

Update GitHub Artifact Actions to v5 (major)
Notable changes
actions/download-artifact (actions/download-artifact)
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

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

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

Compare Source

List of commits

baa5eda (Update GitHub Artifact Actions to v5, 2025-11-13)

v22.5.1

Compare Source

6d625e4 (Run npm install and npm dedupe after any package update, 2025-11-13)
025bd6b (Deduplicate dependencies, 2025-11-13)

v22.5.0

Compare Source

e7f5859 (feat: add update command, 2025-09-15)

List of commits

013bd30 (Update dependency balena-io/balena-cli to v22.5.5, 2025-12-02)

Don't miss a new open-balena release

NewReleases is sending notifications on new releases.