Changelog
How Coframe SDK releases and versioning work
Copy this guide and your current settings as a prompt for your AI agent.
Preview agent promptSee the guide, code and settings included when you copy.
There is no manual version list to track here. The Coframe SDK is delivered directly from the edge, so updates reach your site automatically — without any action on your part. This page explains the release model so you know what to expect when Coframe ships changes.
On this page
01How updates are delivered
When your page loads https://edge.cofra.me/cf.js, the edge worker returns
the current SDK bundle together with your project configuration baked into
the same response. The bundle is cached per-browser for up to 60 seconds
(Cache-Control: private, max-age=60). After that, the browser revalidates
using an ETag; if nothing has changed, the edge returns 304 Not Modified
and no new bytes are transferred. If the SDK or your project configuration
has changed, the fresh bundle is returned immediately.
In practice this means SDK updates and project-config changes propagate to real visitors within about a minute of deployment — with no changes required to your install snippet.
For full details on how the edge delivers the script and why there is no npm package, see Delivery & Versioning.
02Pinning a specific version
If you need a bundle that is guaranteed never to change — for example, to lock a staging environment or audit a specific build — use a versioned URL:
https://edge.cofra.me/cf-static-d1afdec09cc5.jsVersioned bundles embed a 12-hex content hash in the path. They are served
with Cache-Control: public, max-age=31536000, immutable and are retained
in the edge asset map across deployments, so historical script tags continue
to resolve after new releases ship. A non-minified debug variant
(/cf-static-{hash}-non-minified.js) is also available for each build.
Current versions in the deployed edge:
| Component | Version |
|---|---|
Browser SDK (cf.js) |
1.0.1 |
| Edge worker | 1.0.0 |
For the full caching model and bundle URL patterns, see Delivery & Versioning.
03Breaking changes & deprecations
When a release introduces a breaking change or deprecates a command or config field, the details and migration steps are documented in Migration Notes.
# Changelog
How Coframe SDK releases and versioning work
There is no manual version list to track here. The Coframe SDK is delivered
directly from the edge, so updates reach your site automatically — without
any action on your part. This page explains the release model so you know
what to expect when Coframe ships changes.
## How updates are delivered
When your page loads `https://edge.cofra.me/cf.js`, the edge worker returns
the current SDK bundle together with your project configuration baked into
the same response. The bundle is cached per-browser for up to 60 seconds
(`Cache-Control: private, max-age=60`). After that, the browser revalidates
using an `ETag`; if nothing has changed, the edge returns `304 Not Modified`
and no new bytes are transferred. If the SDK or your project configuration
has changed, the fresh bundle is returned immediately.
In practice this means SDK updates and project-config changes propagate to
real visitors within about a minute of deployment — with no changes required
to your install snippet.
For full details on how the edge delivers the script and why there is no npm
package, see [Delivery & Versioning](../docs/delivery-and-versioning.html).
## Pinning a specific version
If you need a bundle that is guaranteed never to change — for example, to
lock a staging environment or audit a specific build — use a versioned URL:
PLAINTEXT
```
https://edge.cofra.me/cf-static-d1afdec09cc5.js
```
Versioned bundles embed a 12-hex content hash in the path. They are served
with `Cache-Control: public, max-age=31536000, immutable` and are retained
in the edge asset map across deployments, so historical script tags continue
to resolve after new releases ship. A non-minified debug variant
(`/cf-static-{hash}-non-minified.js`) is also available for each build.
Current versions in the deployed edge:
Component |
Version |
Browser SDK (`cf.js`) |
`1.0.1` |
Edge worker |
`1.0.0` |
For the full caching model and bundle URL patterns, see
[Delivery & Versioning](../docs/delivery-and-versioning.html).
## Breaking changes & deprecations
When a release introduces a breaking change or deprecates a command or config
field, the details and migration steps are documented in
[Migration Notes](../docs/migration-notes.html).
## Related
- [Delivery & Versioning](../docs/delivery-and-versioning.html) — edge delivery model, caching headers, versioned bundles
- [Migration Notes](../docs/migration-notes.html) — upgrade guidance for breaking changes
- [Config Reference](../docs/config-reference.html) — all `CoframeConfig` fields