Skip to content

fix(ci): make npm cache resilient and versioned (v2)#5

Merged
FallenDeity merged 2 commits intoFallenDeity:masterfrom
teamrobomanipal:fix/ci-cache
Oct 26, 2025
Merged

fix(ci): make npm cache resilient and versioned (v2)#5
FallenDeity merged 2 commits intoFallenDeity:masterfrom
teamrobomanipal:fix/ci-cache

Conversation

@SouriRishik
Copy link
Copy Markdown
Contributor

Problem

  • GitHub Actions runs were intermittently failing at the Node/npm cache step with "Cache service responded with 400", causing CI to fail.

This PR

  • Upgrades actions/setup-node to v4.

  • Adds an explicit actions/cache@v4 step with a versioned key (-v2) and continue-on-error: true to make cache issues non-fatal and allow easy cache invalidation.
    Why

  • Prevents transient cache-service errors from blocking CI and allows forcing a fresh cache by bumping the -v2 suffix.

@vercel
Copy link
Copy Markdown

vercel bot commented Oct 26, 2025

@SouriRishik is attempting to deploy a commit to the fallendeity's projects Team on Vercel.

A member of the Team first needs to authorize it.

@FallenDeity FallenDeity merged commit e6ff2d3 into FallenDeity:master Oct 26, 2025
2 of 3 checks passed
@SouriRishik SouriRishik deleted the fix/ci-cache branch October 26, 2025 17:27
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.

2 participants