Skip to content

docs(rum-legacy): name the current release in the bundle urls #35

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Fiona2016 wants to merge 1 commit into from
Closed

docs(rum-legacy): name the current release in the bundle urls #35

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions packages/rum-legacy/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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/<version>/fc-rum-legacy.js
https://static.flashcat.cloud/browser-sdk/<version>/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
```

`<version>` 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
Expand Down
Loading