Versions And Live Status
- Last reviewed: September 24, 2026
- Release channel: Alpha
- Adapter compatibility line:
0.2
This page separates four facts that are easy to confuse:
- a public source branch can move;
- a tagged release is immutable;
- an installed demo can intentionally run a different exact version; and
- a successful installation is not the same as complete product-family acceptance.
Use the exact tag and artifact recorded for the component you install. Do not
use an unversioned main checkout as a production identity.
Current Validated Component Line
Section titled “Current Validated Component Line”The table records the latest exact component candidates validated for the current OBBBA rollout. It is not a promise that every older sandbox or classic demo has already been upgraded to the same tag.
| Component | Validated tag | Availability | Current role |
|---|---|---|---|
| DiscussionBridge for Discourse | v0.2.0-alpha.50 |
Published release | Receiver, Content Connections, Bridge Records, publication policy, operator UI, and cross-platform work queue |
| DiscussionBridge for Astro | v0.2.0-alpha.34 |
Published release | Astro and Starlight publishing, retrieval, and comments presentation |
| DiscussionBridge for Ghost | v0.2.0-alpha.36 |
Published release | Ghost integration plus bounded hosting-layer publication worker |
| DiscussionBridge for Hugo | v0.2.0-alpha.32 |
Published release | Hugo content materialization and two-phase static deployment |
| DiscussionBridge for Statamic | v0.2.0-alpha.46 |
Published release | One addon used in independently configured Flat, DB, and SSG profiles |
| DiscussionBridge for WordPress | v0.2.0-alpha.42 |
Published release | Native WordPress publication, retrieval, retry, and comments presentation |
| DiscussionBridge Adapter Protocol | v0.2.0-alpha.20 |
Published release; Alpha.21 working candidate is not published | Shared contract and conformance fixtures; no runtime installation |
The Adapter Protocol Alpha.21 work is not a public release yet. Its pending candidate includes the clarified MIT license and current publication-work contract. Documentation must not present it as downloadable until its coherent tag and artifact are published.
OBBBA Demonstration Rollout
Section titled “OBBBA Demonstration Rollout”The forum-scale OBBBA rollout is a real-world Alpha exercise. Status below was verified September 24, 2026. The non-Astro backfill is still processing, so publication counts change while the platform pages remain available for inspection.
| Visible name | Public site | Installed adapter | Rollout state |
|---|---|---|---|
| OBBBA Astro Demo with DiscussionBridge for Astro | Open | v0.2.0-alpha.34 |
Backfill complete; steady-state synchronization |
| OBBBA Ghost Demo with DiscussionBridge for Ghost | Open | v0.2.0-alpha.36 |
Backfill in progress |
| OBBBA Hugo Demo with DiscussionBridge for Hugo | Open | v0.2.0-alpha.32 |
Backfill in progress |
| OBBBA Statamic Flat Demo with DiscussionBridge for Statamic | Open | v0.2.0-alpha.46 |
Backfill in progress |
| OBBBA Statamic DB Demo with DiscussionBridge for Statamic | Open | v0.2.0-alpha.46 |
Backfill in progress |
| OBBBA Statamic SSG Demo with DiscussionBridge for Statamic | Open | v0.2.0-alpha.46 |
Backfill in progress; protected static transaction model |
| OBBBA WordPress Demo with DiscussionBridge for WordPress | Open | v0.2.0-alpha.42 |
Backfill in progress |
The OBBBA source forum is the Repeal OBBBA Forum. These demonstrations are evidence of platform behavior, not templates for a forum’s politics, content policy, or visual identity.
Other Public Demonstrations
Section titled “Other Public Demonstrations”The demo chooser is the stable entry point for maintained public examples. The dedicated demo at The Bridge demonstrates DiscussionBridge for Discourse. “The Bridge” is the demo name, not the generic name of the plugin or receiver.
A Live page proves that the stated public surface is reachable. It does not,
by itself, prove the latest tag, every publishing direction, every presentation
mode, rollback readiness, or completion of the current OBBBA backfill.
How To Read Version Numbers
Section titled “How To Read Version Numbers”DiscussionBridge exposes three related identities:
- Release channel: Alpha, Beta, or stable product-family maturity.
- Adapter compatibility line: the receiver/protocol boundary an adapter
implements, currently
0.2. - Component release: the exact plugin, adapter, addon, or protocol tag and artifact installed in one environment.
Components can advance independently while remaining on the same compatibility line. A newer component number does not imply a new family-wide release, and matching component numbers do not prove matching source bytes.
Installation And Support Evidence
Section titled “Installation And Support Evidence”Record all of the following for an installation or support report:
- component repository and exact tag;
- installed version reported by the component;
- artifact filename and checksum when a packaged artifact is used;
- platform/framework and runtime versions;
- Content Connection identity without its secret;
- publishing direction and presentation mode;
- environment role: demo, sandbox, preproduction, or production; and
- the exact public page and forum topic used for verification.
Historical releases, checksums, and source commits remain available in each repository’s GitHub Releases and in the public versions discussion. They are release evidence, not current installation instructions.
Licensing
Section titled “Licensing”DiscussionBridge components use MIT unless a repository explicitly states
otherwise. DiscussionBridge for Discourse is GPL-2.0-or-later. See
Attribution, Ownership, And Licensing and
the authoritative LICENSE file in each component repository.