Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bump the github-actions-deps group with 4 updates #305

Closed
wants to merge 1 commit into from
Closed

Bump the github-actions-deps group with 4 updates #305

wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 10, 2024 •
edited
Loading

Bumps the github-actions-deps group with 4 updates: actions/checkout, julia-actions/setup-julia, julia-actions/cache and codecov/codecov-action.

Updates actions/checkout from 3 to 4

Release notes

Sourced from actions/checkout's releases.

v4.0.0

What's Changed

New Contributors

Full Changelog: actions/checkout@v3...v4.0.0

v3.6.0

What's Changed

New Contributors

Full Changelog: actions/checkout@v3.5.3...v3.6.0

v3.5.3

What's Changed

New Contributors

Full Changelog: actions/checkout@v3...v3.5.3

v3.5.2

What's Changed

Full Changelog: actions/checkout@v3.5.1...v3.5.2

v3.5.1

What's Changed

New Contributors

... (truncated)

Changelog

Sourced from actions/checkout's changelog.

Changelog

v4.2.1

v4.2.0

v4.1.7

v4.1.6

v4.1.5

v4.1.4

v4.1.3

v4.1.2

v4.1.1

v4.1.0

v4.0.0

... (truncated)

Commits
  • eef6144 Prepare 4.2.1 release (#1925)
  • 6b42224 Add workflow file for publishing releases to immutable action package (#1919)
  • de5a000 Check out other refs/* by commit if provided, fall back to ref (#1924)
  • d632683 Prepare 4.2.0 release (#1878)
  • 6d193bf Bump braces from 3.0.2 to 3.0.3 (#1777)
  • db0cee9 Bump the minor-npm-dependencies group across 1 directory with 4 updates (#1872)
  • b684943 Add Ref and Commit outputs (#1180)
  • 2d7d9f7 Provide explanation for where user email came from (#1869)
  • 9a9194f Bump docker/build-push-action from 5.3.0 to 6.5.0 (#1832)
  • dd960bd Bump docker/login-action in the minor-actions-dependencies group (#1831)
  • Additional commits viewable in compare view

Updates 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: julia-actions/setup-julia@v1.9.6...v2.0.0

v1.9.6: Fix Apple Silicon installation

What's Changed

Deps & CI

New Contributors

Full Changelog: julia-actions/setup-julia@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

Updates 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: julia-actions/cache@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 git@github.com: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

Updates codecov/codecov-action from 3 to 4

Release notes

Sourced from codecov/codecov-action's releases.

v4.0.0

v4 of the Codecov Action uses the CLI as the underlying upload. The CLI has helped to power new features including local upload, the global upload token, and new upcoming features.

Breaking Changes

  • The Codecov Action runs as a node20 action due to node16 deprecation. See this post from GitHub on how to migrate.
  • Tokenless uploading is unsupported. However, PRs made from forks to the upstream public repos will support tokenless (e.g. contributors to OS projects do not need the upstream repo's Codecov token). This doc shows instructions on how to add the Codecov token.
  • OS platforms have been added, though some may not be automatically detected. To see a list of platforms, see our CLI download page
  • Various arguments to the Action have been changed. Please be aware that the arguments match with the CLI's needs

v3 versions and below will not have access to CLI features (e.g. global upload token, ATS).

What's Changed

... (truncated)

Changelog

Sourced from codecov/codecov-action's changelog.

4.0.0-beta.2

Fixes

  • #1085 not adding -n if empty to do-upload command

4.0.0-beta.1

v4 represents a move from the universal uploader to the Codecov CLI. Although this will unlock new features for our users, the CLI is not yet at feature parity with the universal uploader.

Breaking Changes

  • No current support for aarch64 and alpine architectures.
  • Tokenless uploading is unsuported
  • Various arguments to the Action have been removed

3.1.4

Fixes

  • #967 Fix typo in README.md
  • #971 fix: add back in working dir
  • #969 fix: CLI option names for uploader

Dependencies

  • #970 build(deps-dev): bump @​types/node from 18.15.12 to 18.16.3
  • #979 build(deps-dev): bump @​types/node from 20.1.0 to 20.1.2
  • #981 build(deps-dev): bump @​types/node from 20.1.2 to 20.1.4

3.1.3

Fixes

  • #960 fix: allow for aarch64 build

Dependencies

  • #957 build(deps-dev): bump jest-junit from 15.0.0 to 16.0.0
  • #958 build(deps): bump openpgp from 5.7.0 to 5.8.0
  • #959 build(deps-dev): bump @​types/node from 18.15.10 to 18.15.12

3.1.2

Fixes

  • #718 Update README.md
  • #851 Remove unsupported path_to_write_report argument
  • #898 codeql-analysis.yml
  • #901 Update README to contain correct information - inputs and negate feature
  • #955 fix: add in all the extra arguments for uploader

Dependencies

  • #819 build(deps): bump openpgp from 5.4.0 to 5.5.0
  • #835 build(deps): bump node-fetch from 3.2.4 to 3.2.10
  • #840 build(deps): bump ossf/scorecard-action from 1.1.1 to 2.0.4
  • #841 build(deps): bump @​actions/core from 1.9.1 to 1.10.0
  • #843 build(deps): bump @​actions/github from 5.0.3 to 5.1.1
  • #869 build(deps): bump node-fetch from 3.2.10 to 3.3.0
  • #872 build(deps-dev): bump jest-junit from 13.2.0 to 15.0.0
  • #879 build(deps): bump decode-uri-component from 0.2.0 to 0.2.2

... (truncated)

Commits
  • b9fd7d1 chore(release):4.6.0 (#1587)
  • 6f7612c fix: bump eslint parser deps (#1586)
  • 26c7e28 build(deps): bump actions/checkout from 4.1.7 to 4.2.0 (#1583)
  • 6f744f7 build(deps): bump github/codeql-action from 3.26.8 to 3.26.9 (#1584)
  • 543c3d4 chore: fix typo of OSS (#1578)
  • e379426 build(deps-dev): bump @​vercel/ncc from 0.38.1 to 0.38.2 (#1577)
  • 42656e4 build(deps): bump github/codeql-action from 3.26.7 to 3.26.8 (#1575)
  • 2296b6b build(deps-dev): bump eslint from 8.57.0 to 8.57.1 (#1571)
  • bd77bc3 build(deps): bump github/codeql-action from 3.26.6 to 3.26.7 (#1569)
  • 180b964 build(deps-dev): bump @​types/jest from 29.5.12 to 29.5.13 (#1567)
  • 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

@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Oct 10, 2024
This was referenced Oct 10, 2024
Closed
Merged
Closed
Closed
@dependabot
Bump the github-actions-deps group with 4 updates
44bd1a4 
Bumps the github-actions-deps group with 4 updates: [actions/checkout](https://github.com/actions/checkout), [julia-actions/setup-julia](https://github.com/julia-actions/setup-julia), [julia-actions/cache](https://github.com/julia-actions/cache) and [codecov/codecov-action](https://github.com/codecov/codecov-action).


Updates `actions/checkout` from 3 to 4
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](actions/checkout@v3...v4)

Updates `julia-actions/setup-julia` from 1 to 2
- [Release notes](https://github.com/julia-actions/setup-julia/releases)
- [Changelog](https://github.com/julia-actions/setup-julia/blob/master/devdocs/making_a_new_release.md)
- [Commits](julia-actions/setup-julia@v1...v2)

Updates `julia-actions/cache` from 1 to 2
- [Release notes](https://github.com/julia-actions/cache/releases)
- [Changelog](https://github.com/julia-actions/cache/blob/main/devdocs/making_a_new_release.md)
- [Commits](julia-actions/cache@v1...v2)

Updates `codecov/codecov-action` from 3 to 4
- [Release notes](https://github.com/codecov/codecov-action/releases)
- [Changelog](https://github.com/codecov/codecov-action/blob/main/CHANGELOG.md)
- [Commits](codecov/codecov-action@v3...v4)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: github-actions-deps
- dependency-name: julia-actions/setup-julia
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: github-actions-deps
- dependency-name: julia-actions/cache
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: github-actions-deps
- dependency-name: codecov/codecov-action
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: github-actions-deps
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/github_actions/github-actions-deps-c64d6a37e0 branch from 4c5c210 to 44bd1a4 Compare October 10, 2024 13:51
@lgoettgens
Copy link
Collaborator

@dependabot rebase

@dependabot Dependabot
Copy link
Contributor Author

dependabot bot commented on behalf of github Oct 10, 2024

Looks like these dependencies are updatable in another way, so this is no longer needed.

@dependabot dependabot bot closed this Oct 10, 2024
@dependabot dependabot bot deleted the dependabot/github_actions/github-actions-deps-c64d6a37e0 branch October 10, 2024 14:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@lgoettgens