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

chore(deps): update github actions (major) #73

Merged
merged 1 commit into from
Mar 1, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 1, 2024

Mend Renovate

This PR contains the following updates:

Package Type Update Change
JasonEtco/build-and-tag-action action major v1 -> v2
actions/checkout action major v3 -> v4
actions/setup-java action major v2 -> v4
actions/setup-node action major v3 -> v4
codecov/codecov-action action major v3 -> v4
easimon/maximize-build-space action major v7 -> v10

Release Notes

JasonEtco/build-and-tag-action (JasonEtco/build-and-tag-action)

v2

Compare Source

actions/checkout (actions/checkout)

v4

Compare Source

actions/setup-java (actions/setup-java)

v4

Compare Source

v3

Compare Source

actions/setup-node (actions/setup-node)

v4

Compare Source

codecov/codecov-action (codecov/codecov-action)

v4

Compare Source

easimon/maximize-build-space (easimon/maximize-build-space)

v10: Fix: Build Mount folder Ownership

Compare Source

What's Changed

  • fix: if the build mount "deleted" / shadowed the GITHUB_WORKSPACE, do not only recreate it, but also ensure it belongs to the correct owner (runner) again

Full Changelog: easimon/maximize-build-space@v9...v10

v9: Allow build mount path to be a parent of $GITHUB_WORKSPACE

Compare Source

This release adds support for mounting the build volume over a parent folder of $GITHUB_WORKSPACE.

Previously, doing so would remove/shadow the current working directory, and make any later actions/steps fail.

New features:

  • Warn about $BUILD_MOUNT_PATH not being empty and list contents in that case
  • Recreate $GITHUB_WORKSPACE afterwards if missing, so following actions have a working directory to start from.

v8: Ensure mount point directory exists, allow custom ownership

Compare Source

  • When using custom mount points, ensure that the specified target directory exists
  • Allow changing ownership of mounted volume (specify as user:group, defaults to runner:runner, which is the default github actions user/group)

Thanks to @​dawidd6 for the contribution!


Configuration

📅 Schedule: Branch creation - "before 9am" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot merged commit ddc5599 into master Mar 1, 2024
16 checks passed
@renovate renovate bot deleted the renovate/major-github-actions branch March 1, 2024 00:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants