Skip to main content
Each SDK is released independently and carries its own version number — Android’s 0.6.0 has no relationship to Web’s 0.1.0. This page gives the official version lookup page for every platform. Those pages are maintained by the package registries themselves, so they always show the current release.
Most installation examples in the integration guides do not pin a version, so that you get the latest release. When you do need to pin one, look the version up at the link below and write it into your dependency declaration.

​
Latest version per platform

Most platforms ship companion packages alongside the one above — dd-sdk-android-rum and dd-sdk-android-okhttp on Android, FlashcatRUM and FlashcatTrace on iOS, @flashcatcloud/rum on HarmonyOS, and so on. Companion packages of the same platform stay on the same version, so look up the main package and use that version for all of them.

​
Url scheme for the Web CDN bundles

Besides npm, the Web SDK is distributed through a CDN. Each release gets its own directory on the CDN, named for the version with a v prefix:
Take <version> from the npm page in the Web row above and add a v. If npm shows 0.1.0, the url is https://static.flashcat.cloud/browser-sdk/v0.1.0/flashcat-rum.js. Directories of earlier releases are kept indefinitely and never rewritten, so a url always serves the version it names. Upgrading means pointing at a newer release, not re-downloading the same url.
Do not use https://static.flashcat.cloud/browser-sdk/v0/... any more. That is an earlier path named for the major version, and it has not been updated since v0.1.0 — it still resolves, but its contents stay at an old release and will receive no fixes. If your page still references it, switch to a url carrying the full version, as described above.
fc-rum-legacy.js is a separate build for browsers without ES2015 support (IE 9 to 11). It ships from v0.1.0 onwards, is distributed through the CDN only, and is not published to npm. The directories of earlier releases do not contain it.

​
Self-hosted deployments

Private networks usually cannot reach the public CDN, so the bundles have to be served from your own static host. The Web SDK’s files depend on each other through hash-named chunks, so do not pick files by hand — use the sync script in the repository to download a complete set in one go:
With no arguments it downloads the version of the checkout it runs from, and it fails loudly rather than producing a directory with anything missing. See the browser-sdk repository for details.

​
Release notes

For what changed in each Web SDK release, see the browser-sdk CHANGELOG. Release notes for the other platforms are on their package pages linked in the table above.