Versioning

By default, when you embed the recording client, the embed code contains links to our evergreen versions of pipe.js and pipe.css:

<script src="https://cdn.addpipe.com/2.0/pipe.js"></script>
<link rel="stylesheet" href="https://cdn.addpipe.com/2.0/pipe.css">

We frequently update these. Each change gets published our changelog. However, there are cases in which you might prefer to lock your integration to a specific version (to prevent unexpected changes from new releases).

Using Build Slugs for Versioning #

Each recording client release now has a unique build slug that identifies that specific version. You can use this build slug to load an exact version of the recording client.

Version-Specific URL Format #

To load a specific version, use the following URL format:

<script src="https://cdn.addpipe.com/releases/2.0/BUILD_SLUG/pipe.js"></script>
<link rel="stylesheet" href="https://cdn.addpipe.com/releases/2.0/BUILD_SLUG/pipe.css">

Replace BUILD_SLUG with an actual build slug from our changelog.

You can also point to the minified version of pipe.js :

<script src="https://cdn.addpipe.com/releases/2.0/BUILD_SLUG/pipe.min.js"></script>

Or, bypass the AWS CDN, and link directly to the pipe.js hosted on our EU based client delivery servers:

<script src="https://s1.addpipe.com/releases/2.0/BUILD_SLUG/pipe.js"></script>

Finding Build Slugs #

You can find the build slug for any recording client version in our changelog.

Each recording client changelog entry now includes a Build slug field with the unique identifier for that version.

Finding The Currently Used pipe.js Version #

To find the build slug of the pipe.js currently in use, open the page where the recording client is embedded, launch your browser’s developer tools, and check the console for the following line:

pipe-log at 2025-11-19T13:09:42.072Z: Build: 2599b99ea Build date: 18-11-2025

Best Practices #

• Monitor our changelog regularly for important updates and security fixes.
• Use the default, evergreen version of pipe.js and pipe.css to make sure your end users get all the latest updates and fixes right away.
• Always use the pipe.js and pipe.css files from the same build. Do not mix pipe.js from a build with pipe.css from a different build.
• If you’re using a locked version, you might as well host it locally.