[Link-]

Summary

• Release @actions/cache 6.3.0.
• Include the Windows BSD tar scratch-file isolation fix from fix(cache): isolate Windows BSD tar temporary files #2497, which is already merged into main.
• Update compatible runtime and development dependencies, preserve Node 20 support, and resolve npm audit findings.
• Restore the 5.1.0, 5.2.0, and 5.3.0 changelog entries in packages/cache/RELEASES.md.

Changes

Each cache list or extract read now owns a unique scratch directory and cache.tar file. Cleanup is best-effort, so concurrent operations cannot race over shared temporary archives and a cleanup failure does not replace a successful result or the original tool error.

Dependency updates include:

• @actions/glob 0.7
• Node 20-compatible Azure ranges: @azure/core-rest-pipeline ~1.23.0 and @azure/storage-blob ~12.31.0
• semver 7.8.5
• refreshed type dependencies and package lockfile entries

Testing

• Cache TypeScript build on Node.js 20.20 and 24.21
• Full cache Jest suite on Node.js 20.20 and 24.21: 150 passed, 0 failed; 24 Windows-only cases skipped on Linux
• Targeted Prettier and ESLint checks
• Package audit at the moderate threshold: 0 vulnerabilities
• npm pack --dry-run

[Copilot]

Copilot review overview

🟡 Changes recommended

The dependency upgrade excludes Node 20, and duplicated release history should be corrected.

Get a fresh assessment by requesting another Copilot review.

Review effort: Lite
Findings: 1

Open (1)

• Azure dependency upgrade drops Node 20 support · New

What changed in this PR

Prepares the @actions/cache 6.3.0 release with dependency updates and release documentation.

Changes:

• Bumps package and lockfile versions to 6.3.0.
• Updates runtime and development dependencies.
• Documents Windows tar concurrency fixes and historical releases.

File	Summary
packages/​cache/​RELEASES.md	Adds 6.3.0 notes; contains duplicated historical entries.
packages/​cache/​package.json	Updates version and dependencies; introduces Node 20 incompatibility.
packages/​cache/​package-lock.json	Locks updated dependency versions and metadata.

Files not reviewed (1)

• packages/cache/package-lock.json: Generated file

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[chriscmcclure1985-cell]

Suggested change

	- Handle cache write error due to read-only token: detect the `cache write denied:` prefix on cache reservation failures and surface it as a `core.warning` (without failing the run).
	- Handle cache write error due to read-only token: detect the `cache write denied:` prefix on cache reservation failures and surface it as a `core.warning` (without failing the run).- # [ ] []- [ ] ()
	```GitHub Copilot Chat Assistant: Here’s a simple Google Cloud SDK setup and update workflow.
	1. Install the Google Cloud SDK
	- Download from:
	https://cloud.google.com/sdk/docs/install
	- Follow the OS-specific instructions:
	- macOS
	- Windows
	- Linux
	2. Initialize the SDK
	After install, run:
	- gcloud init
	This will:
	- log in to your Google account
	- select or create a Google Cloud project
	- set the default configuration
	You can also set project explicitly:
	- gcloud config set project YOUR_PROJECT_ID
	3. Verify installation
	- gcloud version
	- gcloud components list
	4. Update the SDK
	To update everything:
	- gcloud components update
	This updates:
	- gcloud itself
	- installed components
	- toolchains and add-ons
	5. Install optional components
	Examples:
	- gcloud components install beta
	- gcloud components install alpha
	- gcloud components install kubectl
	- gcloud components install docker-credential-gcr
	6. Check component status
	- gcloud components list
	- gcloud components list --format=table
	7. Set default account and project
	- gcloud auth login
	- gcloud config set project YOUR_PROJECT_ID
	- gcloud config list
	8. Common troubleshooting
	- Reinstall if commands are not recognized:
	- which gcloud
	- gcloud version
	- If PATH is missing, add the SDK bin directory to your shell profile.
	- If the component manager fails, try:
	- gcloud components repair
	9. Recommended recurring workflow
	Use this after new machine setup or regular maintenance:
	- gcloud auth login
	- gcloud config set project YOUR_PROJECT_ID
	- gcloud components update
	- gcloud components install beta
	- gcloud version
	10. Example full workflow
	- gcloud init
	- gcloud config set project my-project-12345
	- gcloud components update
	- gcloud components install kubectl
	- gcloud auth list
	- gcloud projects list
	If you want, I can also give you:
	- a macOS/Linux setup script
	- a Windows PowerShell setup script
	- a checklist for first-time Google Cloud project setup