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 dependency actions/cache to v4 (.github/workflows/linter.yml) (master) #68

Conversation

ivankatliarchuk
Copy link
Member

This PR contains the following updates:

Package Update Change
actions/cache major v3 -> v4.0.2

Release Notes

actions/cache (actions/cache)

v4.0.2

Compare Source

What's Changed

Full Changelog: actions/cache@v4.0.1...v4.0.2

v4.0.1

Compare Source

What's Changed

New Contributors

Full Changelog: actions/cache@v4...v4.0.1

v4.0.0

Compare Source

What's Changed

New Contributors

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

v4

Compare Source

v3.3.3

Compare Source

What's Changed

New Contributors

Full Changelog: actions/cache@v3...v3.3.3

v3.3.2

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v3...v3.3.2

v3.3.1

Compare Source

What's Changed

Full Changelog: actions/cache@v3...v3.3.1

v3.3.0

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v3...v3.3.0

v3.2.6

Compare Source

What's Changed

Full Changelog: actions/cache@v3...v3.2.6

v3.2.5

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v3...v3.2.5

v3.2.4

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v3...v3.2.4

v3.2.3

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v3...v3.2.3

v3.2.2

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v3.2.1...v3.2.2

v3.2.1

Compare Source

What's Changed

Full Changelog: actions/cache@v3.2.0...v3.2.1

v3.2.0

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v3...v3.2.0

v3.0.11

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v3...v3.0.11

v3.0.10

Compare Source

  • Fix a bug with sorting inputs.
  • Update definition for restore-keys in README.md

v3.0.9

Compare Source

  • Enhanced the warning message for cache unavailability in case of GHES.

v3.0.8

Compare Source

What's Changed
  • Fix zstd not working for windows on gnu tar in issues.
  • Allow users to provide a custom timeout as input for aborting cache segment download using the environment variable SEGMENT_DOWNLOAD_TIMEOUT_MIN. Default is 60 minutes.

v3.0.7

Compare Source

What's Changed
  • Fix for the download stuck problem has been added in actions/cache for users who were intermittently facing the issue. As part of this fix, new timeout has been introduced in the download step to stop the download if it doesn't complete within an hour and run the rest of the workflow without erroring out.

v3.0.6

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v3...v3.0.6

v3.0.5

Compare Source

Removed error handling by consuming actions/cache 3.0 toolkit, Now cache server error handling will be done by toolkit.

v3.0.4

Compare Source

In this release, we have fixed the tar creation error while trying to create it with path as ~/ home folder on ubuntu-latest.

v3.0.3

Compare Source

Fixed avoiding empty cache save when no files are available for caching. (https://github.com/actions/cache/issues/624)

v3.0.2

Compare Source

This release adds the support for dynamic cache size cap on GHES.

v3.0.1

Compare Source

  • Added support for caching from GHES 3.5.
  • Fixed download issue for files > 2GB during restore.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, 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 Renovate Bot.

@ivankatliarchuk ivankatliarchuk self-assigned this Mar 24, 2024
@ivankatliarchuk ivankatliarchuk force-pushed the renovate/master-.github/workflows-actions-cache-4.x branch 3 times, most recently from 3f59359 to f2306d7 Compare March 28, 2024 23:10
@ivankatliarchuk ivankatliarchuk force-pushed the renovate/master-.github/workflows-actions-cache-4.x branch from f2306d7 to 0ea7323 Compare April 11, 2024 04:20
@ivankatliarchuk ivankatliarchuk force-pushed the renovate/master-.github/workflows-actions-cache-4.x branch from 0ea7323 to 7043bc7 Compare April 20, 2024 04:22
@ivankatliarchuk ivankatliarchuk force-pushed the renovate/master-.github/workflows-actions-cache-4.x branch from 7043bc7 to 068e01c Compare April 30, 2024 04:23
@ivankatliarchuk ivankatliarchuk force-pushed the renovate/master-.github/workflows-actions-cache-4.x branch from 068e01c to 8c016ab Compare May 20, 2024 04:30
@ivankatliarchuk ivankatliarchuk force-pushed the renovate/master-.github/workflows-actions-cache-4.x branch from 8c016ab to eea2d37 Compare May 27, 2024 04:31
@ivankatliarchuk ivankatliarchuk force-pushed the renovate/master-.github/workflows-actions-cache-4.x branch from eea2d37 to 72b37dc Compare June 12, 2024 04:23
Copy link

stale bot commented Sep 12, 2024

This PR has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. To track this PR (even if closed), please open a corresponding issue if one does not already exist.

@stale stale bot added the stale label Sep 12, 2024
Copy link

stale bot commented Oct 19, 2024

This PR has been automatically closed because it has not had recent activity since being marked as stale. Please reopen when work resumes.

@stale stale bot closed this Oct 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant