fix(publish): purge jsDelivr cache after stable release#1209
Closed
miguel-heygen wants to merge 1 commit into
Closed
fix(publish): purge jsDelivr cache after stable release#1209miguel-heygen wants to merge 1 commit into
miguel-heygen wants to merge 1 commit into
Conversation
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
1 participant
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
After publishing a new stable release to npm, jsDelivr's CDN caches the unversioned URL (
/npm/@hyperframes/core/dist/hyperframe.runtime.iife.js) and doesn't always pick up the new version immediately. This caused demo-next users to get the pre-fix runtime even after v0.6.73 was published — theel.endedguard wasn't active until the cache expired or was manually purged.This PR adds an automatic jsDelivr cache purge step at the end of every stable release publish workflow so the unversioned CDN URLs always serve the latest version immediately.
The purge is skipped for pre-release (alpha/beta) tags since those don't update the
latestdist-tag.Root cause
jsDelivr's unversioned URL cache has a TTL (~10 min for tag resolution) but CDN edge nodes can serve stale content for longer. The
runtime.iife.jsfor 0.6.73 was published but the unversioned URL on Cloudflare/Fastly edges still served the pre-fix build, causing the audioel.endedguard to be missing in the live preview player.Test plan