Bump the all-github-actions group with 2 updates

[dependabot]

Bumps the all-github-actions group with 2 updates: julia-actions/cache and actions/download-artifact.

Updates julia-actions/cache from 2.0.7 to 2.1.0

Release notes

Sourced from julia-actions/cache's releases.

v2.1.0 - New outputs cache-paths and cache-key

What's Changed

New features

• Output cache-paths and cache-key as well by @​penelopeysm in julia-actions/cache#169

Maintenance

• Bump actions/cache from 4.2.0 to 4.2.2 by @​dependabot in julia-actions/cache#165
• Link to Github caching docs from README.md by @​johnomotani in julia-actions/cache#167
• Bump actions/cache from 4.2.2 to 4.2.3 by @​dependabot in julia-actions/cache#172
• Bump dcarbone/install-jq-action from 3.0.1 to 3.1.1 by @​dependabot in julia-actions/cache#171
• Bump pyTooling/Actions from 3.1.1 to 4.2.2 by @​dependabot in julia-actions/cache#170

New Contributors

• @​johnomotani made their first contribution in julia-actions/cache#167
• @​penelopeysm made their first contribution in julia-actions/cache#169

Full Changelog: julia-actions/cache@v2.0.7...v2.1.0

Changelog

Sourced from julia-actions/cache's changelog.

Making a new release

In this guide, as an example, v2.2.0 refers to the version number of the new release that you want to make.

Part 1: Use the Git CLI to create and push the Git tags

Step 1: Create a new lightweight tag of the form vMAJOR.MINOR.PATCH.

git clone [email protected]:julia-actions/cache.git
cd cache
git fetch --all --tags
git checkout main
git --no-pager log -1
Take note of the commit hash here.
Now, create a new lightweight tag of the form vMAJOR.MINOR.PATCH.

Replace commit_hash with the commit hash that you obtained from the
git log -1 step.

Replace v2.2.0 with the actual version number that you want to use.
git tag v2.2.0 commit_hash

Step 2: Once you've created the new release, you need to update the v2 tag to point to the new release. For example, suppose that the previous release was v2.1.0, and suppose that you just created the new release v2.2.0. You need to update the v2 tag so that it points to v2.2.0. Here are the commands:

# Create/update the new v2 tag locally, where the new v2 tag will point to the
# release that you created in the previous step.
#
# Make sure to change `v2.2.0` to the actual value for the tag that you just
# created in the previous step.
#
# The `-f` flag forcibly overwrites the old
# `v2` tag (if it exists).
git tag -f v2 v2.2.0

Step 3: Now you need to push the tags:

# Regular-push the new `v2.2.0` tag:
git push origin tag v2.2.0
Force-push the new v2 tag:
git push origin tag v2 --force

... (truncated)

Commits

• d10a6fd Bump pyTooling/Actions from 3.1.1 to 4.2.2 (#170)
• 1f7b6e0 Bump dcarbone/install-jq-action from 3.0.1 to 3.1.1 (#171)
• c189348 Bump actions/cache from 4.2.2 to 4.2.3 (#172)
• c231b4e Output cache-paths and cache-key as well (#169)
• e5a7946 Link to Github caching docs from README.md (#167)
• 9b3f75e Bump actions/cache from 4.2.0 to 4.2.2 (#165)
• See full diff in compare view

Updates actions/download-artifact from 4.2.1 to 4.3.0

Release notes

Sourced from actions/download-artifact's releases.

v4.3.0

What's Changed

• feat: implement new artifact-ids input by @​GrantBirki in actions/download-artifact#401
• Fix workflow example for downloading by artifact ID by @​joshmgross in actions/download-artifact#402
• Prep for v4.3.0 release by @​robherley in actions/download-artifact#404

New Contributors

• @​GrantBirki made their first contribution in actions/download-artifact#401

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

Commits

• d3f86a1 Merge pull request #404 from actions/robherley/v4.3.0
• fc02353 prep for v4.3.0 release
• 7745437 Merge pull request #402 from actions/joshmgross/download-by-id-example
• 84fc7a0 Remove path filters from Check dist workflow
• 67f2bc3 Fix workflow example for downloading by artifact ID
• 8ea3c2c Merge pull request #401 from actions/download-by-id
• d219c63 add supporting unit tests for artifact downloads with ids
• 54124fb revert getArtifact() changes - for now we have to list and filter by artifa...
• b83057b bundle
• 171183c use the same artifactClient.getArtifact structure as seen above in `isSingl...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions