From faee4d09836e0d9030508fbfd375b77cd4de94b6 Mon Sep 17 00:00:00 2001 From: Fiona Date: Mon, 31 Aug 2026 20:53:36 -0700 Subject: [PATCH] docs(rum-legacy): name the current release in the bundle urls A placeholder makes the reader look the version up before they can fetch anything. Release directories are never overwritten, so a url that names one keeps working: a version that falls behind hands back an older bundle, where the unreleased one it replaced returned 404. --- packages/rum-legacy/README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/packages/rum-legacy/README.md b/packages/rum-legacy/README.md index 6c06a134eb..4d9cb1a3bd 100644 --- a/packages/rum-legacy/README.md +++ b/packages/rum-legacy/README.md @@ -45,12 +45,12 @@ names, which those engines cannot even parse and no runtime guard could catch. Released bundles are served from the CDN under the directory of the release they belong to: ``` -https://static.flashcat.cloud/browser-sdk//fc-rum-legacy.js -https://static.flashcat.cloud/browser-sdk//flashcat-rum.js +https://static.flashcat.cloud/browser-sdk/v0.1.0/fc-rum-legacy.js +https://static.flashcat.cloud/browser-sdk/v0.1.0/flashcat-rum.js ``` -`` is the release tag, `v` prefix included. This build ships from `v0.1.0` onwards; the -directories of earlier releases exist but hold no `fc-rum-legacy.js`. +`v0.1.0` is the current release, and the first one to carry this build: the directories of earlier +releases exist but hold no `fc-rum-legacy.js`. Each release gets its own directory and earlier ones are left as they were, so a url pins the version it names. Updating a self-hosted copy means pointing at the next release, not