omlins / ParallelStencil.jl

Package for writing high-level code for parallel high-performance stencil computations that can be deployed on both GPUs and CPUs
BSD 3-Clause "New" or "Revised" License
323 stars 38 forks source link

Bump julia-actions/setup-julia from 1 to 2 #164

Open dependabot[bot] opened 1 month ago

dependabot[bot] commented 1 month ago

Bumps julia-actions/setup-julia from 1 to 2.

Release notes

Sourced from julia-actions/setup-julia's releases.

v2.0.0 - Update to Node20

What's Changed

Note the rationale for the breaking change was discussed in julia-actions/setup-julia#209

Dependencies and misc

New Contributors

Full Changelog: https://github.com/julia-actions/setup-julia/compare/v1.9.6...v2.0.0

v1.9.6: Fix Apple Silicon installation

What's Changed

Deps & CI

New Contributors

Full Changelog: https://github.com/julia-actions/setup-julia/compare/v1.9.5...v1.9.6

v1.9.5: Maintain mtime of julia build to avoid re-precompilation

A big part of fixing JuliaLang/julia#50667 for julia <1.11 as maintaining the mtime of the julia source files means cached /compiled caches won't be invalidated in new runs where julia has been reinstalled.

What's Changed

Dep updates

... (truncated)

Changelog

Sourced from julia-actions/setup-julia'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 git@github.com:julia-actions/setup-julia.git
cd setup-julia
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
  • a0a0978 Simplify the release process (no more build script or release branches) (#281)
  • 54be0dc Update version on master (#279)
  • 014c323 Resolve min as the earliest compatible Julia version (compatible with the u...
  • b83c8a2 Bump @​types/node from 20.14.11 to 22.5.1 (#277)
  • 8c3db01 Bump ts-jest from 29.2.3 to 29.2.5 (#276)
  • f8f6acf Bump typescript from 5.5.3 to 5.5.4 (#275)
  • f2dfec4 Bump bin from e564658 to 0f674f3 (#272)
  • 3bc2a87 package.json: change version number from 2.2.0 to 2.3.0 (#271)
  • 0c41305 Improve example version instructions. Add info about "lts" if user specifies ...
  • 5956f5e If the user provides default as the value of the arch input, use the runn...
  • 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 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)