ArviZ.jl icon indicating copy to clipboard operation
ArviZ.jl copied to clipboard

Published 20 hours ago • verified publisher icon arviz-devs

Bump julia-actions/cache from 1 to 2

Open dependabot[bot] opened this issue 1 year ago • 0 comments

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

New Contributors

Full Changelog: https://github.com/julia-actions/cache/compare/v1.5.2...v2.0.0

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

What's Changed

... (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 compatibility score

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)

dependabot[bot] avatar Jun 01 '24 15:06 dependabot[bot]