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.1.0 #683

Merged
merged 1 commit into from
Oct 9, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 9, 2024

This PR contains the following updates:

Package Type Update Change Pending
actions/cache action minor v4.0.2 -> v4.1.0 v4.1.1

Release Notes

actions/cache (actions/cache)

v4.1.0

Compare Source

What's Changed
New Contributors

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


Configuration

📅 Schedule: Branch creation - "* 0-4 * * 3" (UTC), 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.

@renovate renovate bot requested a review from thypon as a code owner October 9, 2024 01:35
Copy link

github-actions bot commented Oct 9, 2024

[puLL-Merge] - actions/cache@v4.0.2..v4.1.0

Description

This PR introduces several changes to the actions/cache repository, including updating the version number, adding a new workflow for publishing immutable action versions, deprecating the save-always input, and making various documentation updates.

Changes

Changes

  1. .github/workflows/publish-immutable-actions.yml (New file):

    • Adds a new workflow to publish immutable action versions when a release is published.
  2. README.md:

    • Updates the version numbers for various actions from v3 to v4.
    • Removes mention of the save-always flag from v4 features.
    • Updates the description of restore-keys input.
  3. RELEASES.md:

    • Adds a new entry for version 4.1.0, mentioning the deprecation of save-always input and ensuring cache-hit output is set when a cache is missed.
  4. __tests__/restore.test.ts and __tests__/restoreOnly.test.ts:

    • Updates test cases to reflect changes in cache-hit output behavior.
  5. action.yml:

    • Updates the description of restore-keys input.
    • Adds a deprecation message for the save-always input.
    • Removes save-always from the post-if condition.
  6. caching-strategies.md:

    • Updates version numbers from v3 to v4.
    • Adds a reference to the new "Always save cache" section in the save README.
  7. dist/restore-only/index.js and dist/restore/index.js:

    • Updates the implementation to set cache-hit output to false when no cache is found.
  8. examples.md:

    • Updates version numbers from v3 to v4 throughout the file.
  9. package.json:

    • Updates the version number to 4.1.0.
  10. restore/README.md and restore/action.yml:

    • Updates version numbers and descriptions.
  11. save/README.md:

    • Updates version numbers and adds a new section on "Always save cache" with an example.
  12. src/restoreImpl.ts:

    • Implements the change to set cache-hit output to false when no cache is found.
  13. tips-and-workarounds.md:

    • Updates version numbers from v3 to v4.

Possible Issues

  • The deprecation of the save-always input may affect existing workflows that rely on this feature. Users will need to update their workflows to use the new recommended approach for always saving caches.

Security Hotspots

No significant security issues were identified in this PR.

@thypon thypon merged commit 3bca464 into main Oct 9, 2024
8 checks passed
@thypon thypon deleted the renovate/actions-cache-4.x branch October 9, 2024 09:09
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