Skip to content

OpenCrawl core 0.5.0

Latest

Choose a tag to compare

@duci9y duci9y released this 17 Nov 02:42
3a17ce9

OpenCrawl core v0.5.0

Self-hosted Better Auth now uses the PostgreSQL application database. Accounts,
password hashes, memberships, invitations, browser sessions, signing keys and
CLI/MCP OAuth grants live alongside application state in the database configured
by OPENCRAWL_DATABASE_URL, in a namespace-bound authentication schema.

Breaking change: SQLite authentication is no longer supported

The runtime no longer opens identity.sqlite and has no SQLite authentication
fallback. PostgreSQL is required even when using the optional SQLite FTS5 search
index. OPENCRAWL_IDENTITY_PATH applies only to the legacy import tooling; it
cannot select the authentication backend. Cloud continues to use WorkOS.

New installations use the application PostgreSQL database provided by Compose or
Helm, or an operator-owned external database. No separate authentication database,
hosted OpenCrawl account or authentication service is required.

The self-host integration registry and its durable lifecycle commands also
require the application PostgreSQL database. There is no SQLite registry backend
or fallback. OPENCRAWL_REGISTRY_PATH, like OPENCRAWL_IDENTITY_PATH, is accepted
only by the offline legacy import command. Runtime configuration no longer
exposes either SQLite path.

Board migration now batches writes and verification. Incremental replay preserves
unchanged publication and search rows while retaining message IDs, retry records,
subscriptions, acknowledgment cursors and pending deliveries. This improves the
required upgrade without introducing another runtime storage backend.

Existing installations

This is a breaking release. Migrate an existing SQLite installation separately
before starting the new runtime. Ask your agent to inspect the deployment, take
a matched recovery backup and follow the
application-state upgrade guide.
The existing offline import tools remain available; this release adds no new
migration or compatibility layer.

The application-state upgrade is required for existing installations, including
retained message-board state.
Plan a self-host maintenance window. From the
original checkout, with its private configuration and volumes preserved, run:

./deploy/upgrade.sh --installation deploy --check
./deploy/upgrade.sh --installation deploy --backup /private/new-recovery-directory

For installations created by dev/up, use --installation dev. The coordinated
upgrade preserves the old runtime, stops writers, takes a matched backup, imports
and verifies state, and only then starts the new runtime. Follow the guide for
external services or custom deployments; the standard upgrader does not guess
how to back up those layouts. This self-host maintenance procedure does not
perform or describe a cloud cutover.

Preserve organization and user IDs, password hashes, memberships, signing keys,
OAuth records, private configuration and source data. Do not initialize an empty
replacement account store over an existing installation. Stop old writers before
cutover and verify sign-in, CLI/MCP authorization and retained data afterward.

Rollback requires the previous runtime and the complete matched recovery point;
do not run old binaries against the new storage. See the
restore procedure.

Versions and artifacts

Core 0.5.0 pins the independently published CLI 0.4.94. The PostgreSQL
runtime switch previously landed on main in
PR #312; this minor
release makes the break explicit relative to stable core 0.4.1.

Use the tagged repository for the complete self-host distribution. The attached
runtime archive matches the published core package; SHA256SUMS.txt records its
checksum. Kubernetes users can use the independently versioned Helm 0.2.0
self-host kit with pinned public amd64/arm64 images.

All changes since v0.4.1

Publication verification

Source: 3a17ce99a3c453a18b24cba706d3e6cd8e3da17c (PR #343). The attached archive matches the published registry integrity and this source.

The published package passed a PostgreSQL authentication check covering sign-up, admin enrollment, persisted sessions after connection restart, organization isolation and password recovery. The combined core suite passed 1,237 tests, with 56 optional-service skips and no failures.

Package publication workflow.