Skip to content

Bump the dependencies group across 1 directory with 6 updates#5

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/dependencies-49ab442575
Open

Bump the dependencies group across 1 directory with 6 updates#5
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/dependencies-49ab442575

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Apr 1, 2026

Copy link
Copy Markdown
Contributor

Bumps the dependencies group with 6 updates in the / directory:

Package From To
azure/login 2.3.0 3.0.0
azure/cli 2 3
actions/checkout 5 6
prefix-dev/setup-pixi 0.9.2 0.9.6
actions/upload-artifact 4 7
actions/cache 4 5

Updates azure/login from 2.3.0 to 3.0.0

Release notes

Sourced from azure/login's releases.

Azure Login Action v3.0.0

What's Changed

Full Changelog: Azure/login@v2.3.0...v3.0.0

Commits

Updates azure/cli from 2 to 3

Release notes

Sourced from azure/cli's releases.

GitHub Action for Azure CLI v3

What's Changed

Full Changelog: Azure/cli@v2.2.0...v3

GitHub Action for Azure CLI v3.0.0

What's Changed

Full Changelog: Azure/cli@v2.2.0...v3.0.0

GitHub Action for Azure CLI v2.2.0

What's Changed

New Contributors

Full Changelog: Azure/cli@v2.1.0...v2.2.0

GitHub Action for Azure CLI v2.1.0

What's Changed

New Contributors

Full Changelog: Azure/cli@v2.0.0...v2.1.0

Changelog

Sourced from azure/cli's changelog.

Releasing a new version

Semanting versioning is used to release different versions of the action. Following steps are to be followed :

  1. Create a new branch for every major version.
    Example, releases/v1, releases/v2.
  2. For every minor and patch release for a major version, update the corresponding release branch.
    Example, for releasing v1.1.1, update releases/v1.
  3. Create tags for every new release (major/minor/patch).
    Example,v1.0.0. , v1.0.1, v2.0.1, etc. and also have tags like v1, v2 for every major version release.
  4. On releasing minor and patch versions, update the tag of the corresponding major version.
    Example, for releasing v1.0.1, update the v1 tag to point to the ref of the current release.
    The following commands are to be run on the release\v1 branch so that it picks the latest commit and updates the v1 tag accordingly : (Ensure that you are on same commit locally as you want to release)
  • git tag -fa v1 -m "Update v1 tag"
  • git push origin v1 --force
Commits

Updates actions/checkout from 5 to 6

Release notes

Sourced from actions/checkout's releases.

v6.0.0

What's Changed

Full Changelog: actions/checkout@v5.0.0...v6.0.0

v6-beta

What's Changed

Updated persist-credentials to store the credentials under $RUNNER_TEMP instead of directly in the local git config.

This requires a minimum Actions Runner version of v2.329.0 to access the persisted credentials for Docker container action scenarios.

v5.0.1

What's Changed

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

Changelog

Sourced from actions/checkout's changelog.

Changelog

v6.0.3

v6.0.2

v6.0.1

v6.0.0

v5.0.1

v5.0.0

v4.3.1

v4.3.0

v4.2.2

v4.2.1

v4.2.0

v4.1.7

... (truncated)

Commits

Updates prefix-dev/setup-pixi from 0.9.2 to 0.9.6

Release notes

Sourced from prefix-dev/setup-pixi's releases.

v0.9.6

What's Changed

✨ New features

⬆️ Dependency updates

🤷🏻 Other changes

New Contributors

Full Changelog: prefix-dev/setup-pixi@v0.9.5...v0.9.6

v0.9.5

What's Changed

📝 Documentation

⬆️ Dependency updates

🤷🏻 Other changes

New Contributors

Full Changelog: prefix-dev/setup-pixi@v0.9.4...v0.9.5

v0.9.4

What's Changed

✨ New features

👷🏻 CI

⬆️ Dependency updates

... (truncated)

Commits
  • 5185adf feat: Add persist-credentials option (#266)
  • 92596c3 chore(deps): bump the nodejs group with 6 updates (#264)
  • 68a459a chore(deps): bump the gh-actions group with 5 updates (#263)
  • 8ce6348 add octo-sts (#262)
  • b92f010 Reference latest Pixi version in README (#260)
  • 46d4c99 chore(deps): bump the gh-actions group with 4 updates (#261)
  • 1b2de7f chore(deps): bump dependencies (#259)
  • 6ef6983 chore(deps): bump the nodejs group with 10 dependencies (#257)
  • e6477eb chore(deps): bump Quantco/ui-actions from 1.0.18 to 1.0.19 in the gh-actions ...
  • 33be5ba chore(deps): bump the nodejs group with 7 updates (#250)
  • Additional commits viewable in compare view

Updates actions/upload-artifact from 4 to 7

Release notes

Sourced from actions/upload-artifact's releases.

v7.0.0

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

v6.0.0

v6 - What's new

[!IMPORTANT] actions/upload-artifact@v6 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. v5 had preliminary support for Node.js 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

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

v5.0.0

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.

... (truncated)

Commits
  • 043fb46 Merge pull request #797 from actions/yacaovsnc/update-dependency
  • 634250c Include changes in typespec/ts-http-runtime 0.3.5
  • e454baa Readme: bump all the example versions to v7 (#796)
  • 74fad66 Update the readme with direct upload details (#795)
  • bbbca2d Support direct file uploads (#764)
  • 589182c Upgrade the module to ESM and bump dependencies (#762)
  • 47309c9 Merge pull request #754 from actions/Link-/add-proxy-integration-tests
  • 02a8460 Add proxy integration test
  • b7c566a Merge pull request #745 from actions/upload-artifact-v6-release
  • e516bc8 docs: correct description of Node.js 24 support in README
  • Additional commits viewable in compare view

Updates actions/cache from 4 to 5

Release notes

Sourced from actions/cache's releases.

v5.0.0

[!IMPORTANT] actions/cache@v5 runs on the Node.js 24 runtime and requires a minimum Actions Runner version of 2.327.1.

If you are using self-hosted runners, ensure they are updated before upgrading.


What's Changed

Full Changelog: actions/cache@v4.3.0...v5.0.0

v4.3.0

What's Changed

New Contributors

Full Changelog: actions/cache@v4...v4.3.0

v4.2.4

What's Changed

New Contributors

Full Changelog: actions/cache@v4...v4.2.4

v4.2.3

What's Changed

  • Update to use @​actions/cache 4.0.3 package & prepare for new release by @​salmanmkc in actions/cache#1577 (SAS tokens for cache entries are now masked in debug logs)

New Contributors

Full Changelog: actions/cache@v4.2.2...v4.2.3

... (truncated)

Changelog

Sourced from actions/cache's changelog.

Releases

How to prepare a release

[!NOTE]
Relevant for maintainers with write access only.

  1. Switch to a new branch from main.
  2. Run npm test to ensure all tests are passing.
  3. Update the version in https://github.com/actions/cache/blob/main/package.json.
  4. Run npm run build to update the compiled files.
  5. Update this https://github.com/actions/cache/blob/main/RELEASES.md with the new version and changes in the ## Changelog section.
  6. Run licensed cache to update the license report.
  7. Run licensed status and resolve any warnings by updating the https://github.com/actions/cache/blob/main/.licensed.yml file with the exceptions.
  8. Commit your changes and push your branch upstream.
  9. Open a pull request against main and get it reviewed and merged.
  10. Draft a new release https://github.com/actions/cache/releases use the same version number used in package.json
    1. Create a new tag with the version number.
    2. Auto generate release notes and update them to match the changes you made in RELEASES.md.
    3. Toggle the set as the latest release option.
    4. Publish the release.
  11. Navigate to https://github.com/actions/cache/actions/workflows/release-new-action-version.yml
    1. There should be a workflow run queued with the same version number.
    2. Approve the run to publish the new version and update the major tags for this action.

Changelog

5.0.4

  • Bump minimatch to v3.1.5 (fixes ReDoS via globstar patterns)
  • Bump undici to v6.24.1 (WebSocket decompression bomb protection, header validation fixes)
  • Bump fast-xml-parser to v5.5.6

5.0.3

5.0.2

  • Bump @actions/cache to v5.0.3 #1692

5.0.1

5.0.0

[!IMPORTANT] actions/cache@v5 runs on the Node.js 24 runtime and requires a minimum Actions Runner version of 2.327.1.

... (truncated)

Commits
  • 27d5ce7 Merge pull request #1747 from actions/yacaovsnc/update-dependency
  • f280785 licensed changes
  • 619aeb1 npm run build generated dist files
  • bcf16c2 Update ts-http-runtime to 0.3.5
  • 6682284 Merge pull request #1738 from actions/prepare-v5.0.4
  • e340396 Update RELEASES
  • 8a67110 Add licenses
  • 1865903 Update dependencies & patch security vulnerabilities
  • 5656298 Merge pull request #1722 from RyPeck/patch-1
  • 4e380d1 Fix cache key in examples.md for bun.lock
  • Additional commits viewable in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Apr 1, 2026
@dependabot dependabot Bot changed the title Bump the dependencies group with 6 updates Bump the dependencies group across 1 directory with 6 updates May 1, 2026
@dependabot
dependabot Bot force-pushed the dependabot/github_actions/dependencies-49ab442575 branch from 68b866f to 496e2b1 Compare May 1, 2026 22:19
Bumps the dependencies group with 6 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [azure/login](https://github.com/azure/login) | `2.3.0` | `3.0.0` |
| [azure/cli](https://github.com/azure/cli) | `2` | `3` |
| [actions/checkout](https://github.com/actions/checkout) | `5` | `6` |
| [prefix-dev/setup-pixi](https://github.com/prefix-dev/setup-pixi) | `0.9.2` | `0.9.6` |
| [actions/upload-artifact](https://github.com/actions/upload-artifact) | `4` | `7` |
| [actions/cache](https://github.com/actions/cache) | `4` | `5` |



Updates `azure/login` from 2.3.0 to 3.0.0
- [Release notes](https://github.com/azure/login/releases)
- [Commits](Azure/login@v2.3.0...v3.0.0)

Updates `azure/cli` from 2 to 3
- [Release notes](https://github.com/azure/cli/releases)
- [Changelog](https://github.com/Azure/cli/blob/master/ReleaseProcess.md)
- [Commits](Azure/cli@v2...v3)

Updates `actions/checkout` from 5 to 6
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](actions/checkout@v5...v6)

Updates `prefix-dev/setup-pixi` from 0.9.2 to 0.9.6
- [Release notes](https://github.com/prefix-dev/setup-pixi/releases)
- [Commits](prefix-dev/setup-pixi@v0.9.2...v0.9.6)

Updates `actions/upload-artifact` from 4 to 7
- [Release notes](https://github.com/actions/upload-artifact/releases)
- [Commits](actions/upload-artifact@v4...v7)

Updates `actions/cache` from 4 to 5
- [Release notes](https://github.com/actions/cache/releases)
- [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md)
- [Commits](actions/cache@v4...v5)

---
updated-dependencies:
- dependency-name: actions/cache
  dependency-version: '5'
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: dependencies
- dependency-name: actions/checkout
  dependency-version: '6'
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: dependencies
- dependency-name: actions/upload-artifact
  dependency-version: '7'
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: dependencies
- dependency-name: azure/cli
  dependency-version: '3'
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: dependencies
- dependency-name: azure/login
  dependency-version: 3.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: dependencies
- dependency-name: prefix-dev/setup-pixi
  dependency-version: 0.9.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot
dependabot Bot force-pushed the dependabot/github_actions/dependencies-49ab442575 branch from 496e2b1 to 9311923 Compare June 3, 2026 03:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants