fix: upgrade to actions/cache@v5 (legacy cache service sunset)#8
Merged
lucasgrvarela merged 1 commit intodevelopfrom Feb 20, 2026
Merged
fix: upgrade to actions/cache@v5 (legacy cache service sunset)#8lucasgrvarela merged 1 commit intodevelopfrom
lucasgrvarela merged 1 commit intodevelopfrom
Conversation
hgdata/cache@v3 (v3.3.x) uses the legacy cache service which was sunset on Feb 1 2025. Every cache save has been silently failing with 'Our services aren't available right now' for over a year. actions/cache@v5 uses the current cache service v2 APIs.
lucasgrvarela
approved these changes
Feb 20, 2026
|
🎉 This PR is included in version 1.0.6 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
hgdata/cache/restore@v3andhgdata/cache/save@v3withactions/cache/restore@v5andactions/cache/save@v5Problem
The
hgdata/cachefork is atv3.3.x, which uses the legacy GitHub Actions cache service that was sunset on February 1, 2025. Every cache save/restore has been silently failing across all repos that use this action:This means no Elixir CI job has had working dependency or build caching for over a year. Every run does a full cold build (~5 min setup instead of ~1 min).
Root Cause
GitHub deprecated the legacy cache service and requires
actions/cachev3.4.0+ or v4.2.0+ for the new cache service v2 APIs. Thehgdata/cachefork only has up tov4.1.2, which is also before the cutoff (v4.2.0is required). See: https://github.com/actions/cache#readmeFix
This PR uses
actions/cache@v5directly (upstream) since nohgdata/cacheversion has a working backend.Follow-up: sync the hgdata/cache fork
The
hgdata/cachefork should be synced with upstreamactions/cacheso that other repos usinghgdata/cache@v3orhgdata/cache@v4also get the fix. The fork needs to be updated to at least:v3tag → upstreamv3.4.0+v4tag → upstreamv4.2.0+Once that's done, this action can switch back from
actions/cache@v5tohgdata/cache@v4(or@v5once forked).Verification
Tested on HGData/vulcan PR #2183 — deps cache restores successfully across jobs, build cache saves and restores correctly.