Release Channels

Stable

https://cdn.flowplayer.com/releases/native/stable/:asset

Well-tested and battle hardened, generally have been through at least two rounds of feedback to ensure code quality.

Canary (Bleeding Edge)

https://cdn.flowplayer.com/releases/native/canary/:asset

We do perform internal testing before deployed, but every once in a while bugs might get through. Ideal for verifying bug fixes before changing production code or trying new features before they are in wide release. This was previously called edge , the old links like https://cdn.flowplayer.com/releases/native/edge/:asset will of course continue to work.

Immutable Semver

https://cdn.flowplayer.com/releases/native/v:semver/:asset

When version locking is required by your development team. These assets are never changed once deployed, hence immutable. Each stable release is tagged with a semver version and deployed here.

Async cloud players

The format for calling a cloud player to use a release channel is https://cdn.flowplayer.com/players/[playerid]/native/flowplayer.async.js?release_channel=[stable|canary] resp. https://cdn.flowplayer.com/players/[playerid]/native/flowplayer.async.js?release_channel=v[semver]

Changelogs

All release channels have a changelog auto-generated from our commit history that follows the format:

https://cdn.flowplayer.com/releases/native/:channel/changelog.:format

format can be html or xml in this case. The xml formats allow integrations into your SlackOps channels via the Slack RSS plugin.

An example changelog to demonstrate our url format would be https://cdn.flowplayer.com/releases/native/stable/changelog.html.

Additionally there is a prettified changelog for stable right here.