Releases
PulsePoint v2 is the stable, maintained runtime and the only version these docs cover. v1, the original runtime, is end-of-life: it is no longer maintained.
How releases work
-
A release line is a separate runtime, not a version number.
v2 ships as
pp-reactive-v2.min.js. It has a different API and server contract from v1, so it is not a drop-in replacement for v1 code. - A line is updated in place. New builds of a line replace the file at the same URL; there are no numbered point releases. Every behavior change in v2 is recorded by date in the Runtime Changelog.
- Stable is the maintained line. Fixes, features and performance work all land there. Today that is v2.
- End-of-life means no longer maintained: it receives no fixes of any kind. v1 is end-of-life.
Use v2 for every project. If you still run a v1 application, plan its move to v2; the migration notes are in the project README.
Release schedule
Release lines
| Line | Runtime file | First released | Last updated | Status | Details |
|---|---|---|---|---|---|
| v2 | pp-reactive-v2.min.js | Apr 09, 2026 | Sep 30, 2026 |
Stable
All projects |
|
| v1 | pp-reactive-v1.js | Nov 22, 2025 | Feb 12, 2026 |
End-of-life
Migrate to v2 |
First released is the day the runtime file was first published. Last updated is the day the build now being served was published.
Loading a release
From the CDN
https://pulse-point-cdn.pages.dev serves the latest v2 build. Because the URL is updated in
place, a page that imports it picks up new builds automatically.
<script type="module">
import { ComponentInit as PP } from "https://pulse-point-cdn.pages.dev/pp-reactive-v2.min.js";
PP.bootstrap();
</script>Pinning a build
To control when your application takes an update, download the file and serve it from your own assets, as Installation describes. Before you replace a pinned copy, read the Runtime Changelog entries since the copy's date. Its backend updates list what a server integration should add.
Through a framework
Frameworks with PulsePoint built in, such as Caspian, Prisma PHP and Rahti, ship their own
copy of pp-reactive-v2.min.js and update it in their own releases. That
copy can be older than the CDN build; check your framework's release notes against
the changelog dates. See
Implement In Your Backend.