Bump julia-actions/cache from 1 to 2

[dependabot]

Bumps julia-actions/cache from 1 to 2.

Release notes

Sourced from julia-actions/cache's releases.

v2.0.0

Breaking Changes ⚠️

v2.0.0 requires node20. This is a breaking change, because node20 does not support the following operating systems:

• Red Hat Enterprise Linux 7
• CentOS 7
• Oracle Linux 7
• Debian 9
• Ubuntu 16.04
• Linux Mint 18
• openSUSE 15
• SUSE Enterprise Linux (SLES) 12 SP2
• Windows 7 64-bit
• Windows 8.1 64-bit

Therefore, if you are using self-hosted runners on one of the above operating systems, you won't be able to run v2 of this action.

In contrast, v1 of this action uses node16.

What's Changed

• fix: Attempt to install jq on all runners by @​musoke in julia-actions/cache#105
• Pin third party action to hash by @​SaschaMann in julia-actions/cache#106
• Mention why the extra permissions are required by @​rikhuijzer in julia-actions/cache#108
• More accurate info about GitHub cache retion policy by @​giordano in julia-actions/cache#111
• Only run Dependabot once per month, but increase the PR limit by @​DilumAluthge in julia-actions/cache#115
• Update actions/cache to v3.3.3 by @​IanButterworth in julia-actions/cache#121
• Bump julia-actions/setup-julia from 1 to 2 by @​dependabot in julia-actions/cache#116
• Bump actions/checkout from 4.1.1 to 4.1.2 by @​dependabot in julia-actions/cache#118
• Bump pyTooling/Actions from 0.4.6 to 1.0.1 by @​dependabot in julia-actions/cache#117
• update setup-julia to v2 in readme by @​IanButterworth in julia-actions/cache#124
• Bump actions/checkout from 4.1.2 to 4.1.4 by @​dependabot in julia-actions/cache#126
• Bump pyTooling/Actions from 1.0.1 to 1.0.5 by @​dependabot in julia-actions/cache#127
• Bump actions/cache from 3.3.3 to 4.0.2 by @​dependabot in julia-actions/cache#123

New Contributors

• @​musoke made their first contribution in julia-actions/cache#105
• @​giordano made their first contribution in julia-actions/cache#111
• @​DilumAluthge made their first contribution in julia-actions/cache#115

Full Changelog: julia-actions/cache@v1.5.2...v2.0.0

v1.5.2: Cache tidy fixes. Existing registry fix.

What's Changed

• Delete cache entries only on the workflow branch by @​omus in julia-actions/cache#97
• Test cache action against Julia 1.0 and nightly by @​omus in julia-actions/cache#101
• Avoid corrupting existing cloned Julia registries by @​omus in julia-actions/cache#102
• Pass cache-name between save/restore jobs by @​omus in julia-actions/cache#103
• make depot if not restored by @​IanButterworth in julia-actions/cache#91

... (truncated)

Changelog

Sourced from julia-actions/cache's changelog.

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

Part 2: Create the GitHub Release

Go to the Releases section of this repo and create a new release (using the GitHub web interface).

... (truncated)

Commits

• d48542b Bump actions/cache from 3.3.3 to 4.0.2 (#123)
• caa6556 Bump pyTooling/Actions from 1.0.1 to 1.0.5 (#127)
• 1c20782 Bump actions/checkout from 4.1.2 to 4.1.4 (#126)
• 4b23ab7 update setup-julia to v2 in readme (#124)
• cc87ef3 Bump pyTooling/Actions from 0.4.6 to 1.0.1 (#117)
• c363897 Bump actions/checkout from 4.1.1 to 4.1.2 (#118)
• 1b0706c Bump julia-actions/setup-julia from 1 to 2 (#116)
• 8b63b4a Update actions/cache to v3.3.3 (#121)
• 0413f3b Only run Dependabot once per month, but increase the PR limit (#115)
• e8521d4 More accurate info about GitHub cache retion policy (#111)
• 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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.20%. Comparing base (edcde51) to head (bd2731b).

Additional details and impacted files

@@           Coverage Diff           @@
##           master      #16   +/-   ##
=======================================
  Coverage   94.20%   94.20%           
=======================================
  Files           4        4           
  Lines          69       69           
=======================================
  Hits           65       65           
  Misses          4        4           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.