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.

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

Bump the all-actions group with 4 updates #50

Merged
merged 1 commit into from
Mar 18, 2025

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 18, 2025

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

Updates actions/checkout from 2 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.2

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

... (truncated)

Commits

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 [email protected]: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
  • 5c9647d Bump @​types/node from 22.7.5 to 22.9.0 (#301)
  • 17468e8 Bump @​types/jest from 29.5.13 to 29.5.14 (#298)
  • c861e46 add warning if requesting x64 on apple silicon runners (#300)
  • 2fa1802 README examples: '1' for the latest v1 (#296)
  • 05e75bd Bump julia-actions/setup-julia from 2.5.0 to 2.6.0 (#295)
  • 9b79636 Bump typescript from 5.6.2 to 5.6.3 (#294)
  • 0360370 Bump @​vercel/ncc from 0.38.1 to 0.38.2 (#287)
  • 4e3f1d6 Bump @​actions/core from 1.10.1 to 1.11.1 (#291)
  • 1068b5e Change LTS 1.6 -> 1.10 (#290)
  • f42f7fb Bump @​types/async-retry from 1.4.8 to 1.4.9 (#292)
  • Additional commits viewable in compare view

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 [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

Updates codecov/codecov-action from 2 to 5

Release notes

Sourced from codecov/codecov-action's releases.

v5.0.0

v5 Release

v5 of the Codecov GitHub Action will use the Codecov Wrapper to encapsulate the CLI. This will help ensure that the Action gets updates quicker.

Migration Guide

The v5 release also coincides with the opt-out feature for tokens for public repositories. In the Global Upload Token section of the settings page of an organization in codecov.io, you can set the ability for Codecov to receive a coverage reports from any source. This will allow contributors or other members of a repository to upload without needing access to the Codecov token. For more details see how to upload without a token.

[!WARNING]
The following arguments have been changed

  • file (this has been deprecated in favor of files)
  • plugin (this has been deprecated in favor of plugins)

The following arguments have been added:

  • binary
  • gcov_args
  • gcov_executable
  • gcov_ignore
  • gcov_include
  • report_type
  • skip_validation
  • swift_project

You can see their usage in the action.yml file.

What's Changed

... (truncated)

Changelog

Sourced from codecov/codecov-action's changelog.

v5 Release

v5 of the Codecov GitHub Action will use the Codecov Wrapper to encapsulate the CLI. This will help ensure that the Action gets updates quicker.

Migration Guide

The v5 release also coincides with the opt-out feature for tokens for public repositories. In the Global Upload Token section of the settings page of an organization in codecov.io, you can set the ability for Codecov to receive a coverage reports from any source. This will allow contributors or other members of a repository to upload without needing access to the Codecov token. For more details see how to upload without a token.

[!WARNING] The following arguments have been changed

  • file (this has been deprecated in favor of files)
  • plugin (this has been deprecated in favor of plugins)

The following arguments have been added:

  • binary
  • gcov_args
  • gcov_executable
  • gcov_ignore
  • gcov_include
  • report_type
  • skip_validation
  • swift_project

You can see their usage in the action.yml file.

What's Changed

... (truncated)

Commits
  • 0565863 chore(release): 5.4.0 (#1781)
  • c545d7b update wrapper submodule to 0.2.0, add recurse_submodules arg (#1780)
  • 2488e99 build(deps): bump actions/upload-artifact from 4.6.0 to 4.6.1 (#1775)
  • a46c158 build(deps): bump ossf/scorecard-action from 2.4.0 to 2.4.1 (#1776)
  • 062ee7e build(deps): bump github/codeql-action from 3.28.9 to 3.28.10 (#1777)
  • 1fecca8 Clarify in README that use_pypi bypasses integrity checks too (#1773)
  • 2e6e9c5 Fix use of safe.directory inside containers (#1768)
  • a5dc5a5 Fix description for report_type input (#1770)
  • 4898080 build(deps): bump github/codeql-action from 3.28.8 to 3.28.9 (#1765)
  • 5efa07b Fix a typo in the example (#1758)
  • 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

Bumps the all-actions 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 2 to 4
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](actions/checkout@v2...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 2 to 5
- [Release notes](https://github.com/codecov/codecov-action/releases)
- [Changelog](https://github.com/codecov/codecov-action/blob/main/CHANGELOG.md)
- [Commits](codecov/codecov-action@v2...v5)

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

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Mar 18, 2025
Copy link

codecov bot commented Mar 18, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.97%. Comparing base (a994463) to head (857ca64).
Report is 5 commits behind head on main.

❗ There is a different number of reports uploaded between BASE (a994463) and HEAD (857ca64). Click for more details.

HEAD has 6 uploads less than BASE
Flag BASE (a994463) HEAD (857ca64)
8 2
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #50      +/-   ##
==========================================
- Coverage   91.66%   82.97%   -8.69%     
==========================================
  Files           3        3              
  Lines          96       94       -2     
==========================================
- Hits           88       78      -10     
- Misses          8       16       +8     

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

🚀 New features to boost your workflow:
  • Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@timholy timholy merged commit e11b408 into main Mar 18, 2025
5 of 8 checks passed
@timholy timholy deleted the dependabot/github_actions/all-actions-0a23896519 branch March 18, 2025 18:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant