mirror of
				https://github.com/actions/cache.git
				synced 2025-11-04 13:29:10 +08:00 
			
		
		
		
	Update RELEASES.md
This commit is contained in:
		
							
								
								
									
										17
									
								
								README.md
									
									
									
									
									
								
							
							
						
						
									
										17
									
								
								README.md
									
									
									
									
									
								
							@@ -3,6 +3,7 @@
 | 
			
		||||
This action allows caching dependencies and build outputs to improve workflow execution time.
 | 
			
		||||
 | 
			
		||||
>Two other actions are available in addition to the primary `cache` action:
 | 
			
		||||
>
 | 
			
		||||
>* [Restore action](./restore/README.md)
 | 
			
		||||
>* [Save action](./save/README.md)
 | 
			
		||||
 | 
			
		||||
@@ -14,6 +15,22 @@ See ["Caching dependencies to speed up workflows"](https://docs.github.com/en/ac
 | 
			
		||||
 | 
			
		||||
## What's New
 | 
			
		||||
 | 
			
		||||
### ⚠️ Important changes
 | 
			
		||||
 | 
			
		||||
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.
 | 
			
		||||
 | 
			
		||||
Read more about the change & access the migration guide: [reference to the announcement](https://github.com/actions/cache/discussions/1510).
 | 
			
		||||
 | 
			
		||||
### v4
 | 
			
		||||
 | 
			
		||||
* Updated to node 20
 | 
			
		||||
 
 | 
			
		||||
							
								
								
									
										14
									
								
								RELEASES.md
									
									
									
									
									
								
							
							
						
						
									
										14
									
								
								RELEASES.md
									
									
									
									
									
								
							@@ -1,5 +1,19 @@
 | 
			
		||||
# Releases
 | 
			
		||||
 | 
			
		||||
### 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://github.com/actions/cache/pull/1474)
 | 
			
		||||
 
 | 
			
		||||
		Reference in New Issue
	
	Block a user