Repository navigation
fix(ci): warm the new tag on jsDelivr before notifying the backend - #11
Merged
Merged
Conversation
The publish workflow failed at "Notify backend" on every run: it cut the tag, slept 5s, then asked the backend to refresh by that brand-new tag. jsDelivr hadn't pulled the cold tag from GitHub yet, so the backend's fetch timed out -> 502 -> `curl -fsS` exit 22. Poll jsDelivr for the new tag until it actually serves it (<=60s) before notifying, retry the backend POST a few times for any residual cold-edge race, and treat a final failure as a `::warning::` (non-fatal) since the backend's L2 TTL refresh still propagates the tag. Companion: fleetifydev/fleetify-monorepo widens the backend's forced-refresh fetch timeout so a cold pull no longer 502s. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
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.
Problem
The
publishworkflow failed at Notify backend on every run (~10 days): after cutting the immutable tag itsleep 5'd, then POSTed/api/internal/catalog/refreshwith the brand-new tag. jsDelivr hadn't pulled that cold tag from GitHub yet, so the backend's force-fetch timed out → 502 →curl -fsSexit 22 → red CI.The catalog itself published fine (tag cut, dist committed,
@mainpurged) — only the instant-propagation notify failed.Fix
cdn.jsdelivr.net/gh/...@${TAG}/dist/models.jsonuntil it 200s (≤60s) before notifying, so the backend fetches a hot edge.::warning::instead of failing the job — the backend's L2 TTL refresh still propagates the tag.Companion
fleetifydev/fleetify-monorepo#44widens the backend's forced-refresh fetch budget (4s → 15s) so a cold pull no longer 502s even without the warm-up.🤖 Generated with Claude Code