Visitar URL original
Prepare `v4.3.0` release by Link- · Pull Request #1655 · actions/cache · GitHub
Skip to content

Prepare v4.3.0 release - #1655

Merged
Link- merged 2 commits into
mainfrom
Link-/prepare-4.3.0
Sep 24, 2025
Merged

Link- merged 2 commits into
mainfrom
Link-/prepare-4.3.0

Conversation

@Link-

@Link- Link- commented Sep 24, 2025 •

Copy link
Copy Markdown
Member

Description

Fixes: https://github.com/github/actions-persistence/issues/199

Motivation and Context

Preparing new release

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation (add or update README or docs)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@Link-
Link- requested a review from a team as a code owner September 24, 2025 13:25
Copilot AI review requested due to automatic review settings September 24, 2025 13:25

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR upgrades the @actions/cache dependency from v4.0.5 to v4.1.0 and bumps the package version to 4.3.0 to prepare for release. The changes ensure the action uses the latest version of the cache toolkit with any bug fixes or improvements.

  • Upgrade @actions/cache dependency from ^4.0.5 to ^4.1.0
  • Bump package version from 4.2.4 to 4.3.0
  • Add release notes for version 4.3.0

Reviewed Changes

Copilot reviewed 2 out of 7 changed files in this pull request and generated no comments.

File Description
package.json Updates package version to 4.3.0 and upgrades @actions/cache dependency to ^4.1.0
RELEASES.md Adds release notes for version 4.3.0 documenting the @actions/cache upgrade

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

@Link- Link- self-assigned this Sep 24, 2025
@Link- Link- changed the title Upgrade actions/cache to 4.1.0 and prepare 4.3.0 release Prepare v4.3.0 release Sep 24, 2025
@Link-
Link- merged commit 0057852 into main Sep 24, 2025
@Link-
Link- deleted the Link-/prepare-4.3.0 branch September 24, 2025 13:47
mergify Bot added a commit to ArcadeData/arcadedb that referenced this pull request Sep 29, 2025
Bumps [actions/cache](https://github.com/actions/cache) from 4.2.4 to 4.3.0.
Release notes

*Sourced from [actions/cache's releases](https://github.com/actions/cache/releases).*

> v4.3.0
> ------
>
> What's Changed
> --------------
>
> * Add note on runner versions by [`@​GhadimiR`](https://github.com/GhadimiR) in [actions/cache#1642](https://redirect.github.com/actions/cache/pull/1642)
> * Prepare `v4.3.0` release by [`@​Link`](https://github.com/Link)- in [actions/cache#1655](https://redirect.github.com/actions/cache/pull/1655)
>
> New Contributors
> ----------------
>
> * [`@​GhadimiR`](https://github.com/GhadimiR) made their first contribution in [actions/cache#1642](https://redirect.github.com/actions/cache/pull/1642)
>
> **Full Changelog**: <actions/cache@v4...v4.3.0>


Changelog

*Sourced from [actions/cache's changelog](https://github.com/actions/cache/blob/main/RELEASES.md).*

> Releases
> ========
>
> ### 4.3.0
>
> * Bump `@actions/cache` to [v4.1.0](https://redirect.github.com/actions/toolkit/pull/2132)
>
> ### 4.2.4
>
> * Bump `@actions/cache` to v4.0.5
>
> ### 4.2.3
>
> * Bump `@actions/cache` to v4.0.3 (obfuscates SAS token in debug logs for cache entries)
>
> ### 4.2.2
>
> * Bump `@actions/cache` to v4.0.2
>
> ### 4.2.1
>
> * Bump `@actions/cache` to v4.0.1
>
> ### 4.2.0
>
> TLDR; The cache backend service has been rewritten from the ground up for improved performance and reliability. [actions/cache](https://github.com/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](https://github.com/actions/cache) will fail.
>
> Upgrading to the recommended versions will not break your workflows.
>
> ### 4.1.2
>
> * Add GitHub Enterprise Cloud instances hostname filters to inform API endpoint choices - [#1474](https://redirect.github.com/actions/cache/pull/1474)
> * Security fix: Bump braces from 3.0.2 to 3.0.3 - [#1475](https://redirect.github.com/actions/cache/pull/1475)
>
> ### 4.1.1
>
> * Restore original behavior of `cache-hit` output - [#1467](https://redirect.github.com/actions/cache/pull/1467)
>
> ### 4.1.0
>
> * Ensure `cache-hit` output is set when a cache is missed - [#1404](https://redirect.github.com/actions/cache/pull/1404)
> * Deprecate `save-always` input - [#1452](https://redirect.github.com/actions/cache/pull/1452)

... (truncated)


Commits

* [`0057852`](actions/cache@0057852) Merge pull request [#1655](https://redirect.github.com/actions/cache/issues/1655) from actions/Link-/prepare-4.3.0
* [`4f5ea67`](actions/cache@4f5ea67) Update licensed cache
* [`9fcad95`](actions/cache@9fcad95) Upgrade actions/cache to 4.1.0 and prepare 4.3.0 release
* [`638ed79`](actions/cache@638ed79) Merge pull request [#1642](https://redirect.github.com/actions/cache/issues/1642) from actions/GhadimiR-patch-1
* [`3862dcc`](actions/cache@3862dcc) Add note on runner versions
* See full diff in [compare view](actions/cache@0400d5f...0057852)
  
[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility\_score?dependency-name=actions/cache&package-manager=github\_actions&previous-version=4.2.4&new-version=4.3.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
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-automerge-start)
[//]: # (dependabot-automerge-end)
---
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  ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
@arejon880-bit

ghost commented Nov 22, 2025

Copy link
Copy Markdown

Description

Fixes: https://github.com/github/actions-persistence/issues/199

Motivation and Context

Preparing new release

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation (add or update README or docs)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

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.

5 participants