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 actions/cache action to v4 #112

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 10, 2024

This PR contains the following updates:

Package Type Update Change
actions/cache action major v3.0.11 -> v4.2.0

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

actions/cache (actions/cache)

v4.2.0

Compare Source

⚠️ Important Changes

The cache backend service has been rewritten from the ground up for improved performance and reliability. actions/cache now integrates with the new cache service (v2) APIs.

The new service will gradually roll out as of February 1st, 2025. The legacy service will also be sunset on the same date. Changes in these release are fully backward compatible.

We are deprecating some versions of this action. We recommend upgrading to version v4 or v3 as soon as possible before February 1st, 2025. (Upgrade instructions below).

If you are using pinned SHAs, please use the SHAs of versions v4.2.0 or v3.4.0

If you do not upgrade, all workflow runs using any of the deprecated actions/cache will fail.

Upgrading to the recommended versions will not break your workflows.

Read more about the change & access the migration guide: reference to the announcement.

Minor changes

Minor and patch version updates for these dependencies:

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

v4.1.2

Compare Source

What's Changed
New Contributors

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

v4.1.1

Compare Source

What's Changed

Full Changelog: actions/cache@v4.1.0...v4.1.1

v4.1.0

Compare Source

What's Changed
New Contributors

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

v4.0.2

Compare Source

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

v3.4.0

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


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 becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

This PR was generated by Mend Renovate. View the repository job log.

Copy link

coderabbitai bot commented Mar 10, 2024

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@renovate renovate bot force-pushed the renovate/actions-cache-4.x branch from b40a099 to 04b6d43 Compare March 19, 2024 19:46
@renovate renovate bot force-pushed the renovate/actions-cache-4.x branch 2 times, most recently from 3cdb19f to d9e76ae Compare October 8, 2024 19:48
@renovate renovate bot force-pushed the renovate/actions-cache-4.x branch from d9e76ae to ab198f0 Compare October 22, 2024 15:13
@renovate renovate bot force-pushed the renovate/actions-cache-4.x branch from ab198f0 to ef1dc0d Compare December 5, 2024 18:39
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