Skip to content

v1.5.0-rc.2

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 19 Nov 20:10
· 3 commits to main since this release

Release Notes 1.5.0-rc.2

Released: 2026-11-19

Second release candidate for 1.5.0. The work here is correctness and integrity hardening on top of rc.1: archived text no longer comes back as a timestamp, device sign-in approval refuses API keys, graph restore stops scanning whole tables on SurrealDB 4.0, and the CI pipeline now actually reruns checks when a project's own lockfile moves. The SurrealDB runtime moves to 4.0.1 across every deployment path.

🌟 Highlights

🐛 Restores keep text as text

Archives store every datetime as ISO text, and the restore path used to deserialize uniformly, so any string that merely read like a timestamp (titles, chunk bodies, settings values) came back as a datetime. The destination schema is now the authority: fetch_restore_fields() and fetch_datetime_fields() in schema_invariants.py read INFO FOR TABLE to learn which paths are declared datetime, and convert_declared_fields() converts only at those paths, including option<datetime>, arrays, and nested paths. content_archive.py and auth_archive.py both route through it; retained operation tables keep archived values untouched.

🔒 Device sign-in approval requires a session, never an API key

The device approval page resolved its approver with resolve_claims, which answers for an API key as readily as for a session. A personal key with api:write could start a device flow and approve it itself, and the device collected a full session with a refresh token: none of the key's scopes or project limits, and still valid after the key was revoked. Bot keys were already refused; personal keys were not. Both device pages now read the approver through the new _session_claims() helper in apps/api/src/sibyl/api/routes/auth.py, so a key is treated as signed out. A session token sent as a bearer still approves, which is what the end-to-end auth flow does. API-key requests to POST /api/auth/device/verify now redirect with error=not_authenticated.

⚡️ Flat restore batches on SurrealDB 4.0

SurrealDB 4.0 plans filters on client parameters as index lookups, but filters on closure arguments, FOR variables, or block LET variables scan the entire table. The old FOR $row IN $rows { LET $uuid = ... } pattern therefore paid a full scan per restored row, scaling quadratically with destination size. graph_companion_restore.py and source_archive_store.py now build clumped, client-parameter reads through new clumped(), _held(), _association_lookup(), and _unit_state_projection() helpers, indexing results with _by_uuid() / _by_identity() maps, with _PROBES_PER_STATEMENT = 32 bounding uniqueness probes per statement.

🐛 sibyld db restore exits nonzero when it fails

apps/api/src/sibyl/cli/db.py now raises typer.Exit(code=1) both on exception and when the restore result reports failure, and the end-of-run message is an error rather than a warning: "Restore failed; the counts below are what landed before it stopped". Scripts and CI jobs that wrapped the command will now see the failure.

🔧 A project's own lockfile reruns its checks

Every Python task inherited the workspace lockfile as an input, but hooks and apps/e2e resolve their tools from lockfiles of their own, which were inputs to nothing. A bump touching only one of them left task hashes unchanged, so moon replayed cached lint and typecheck results and reported a new toolchain green without running it. That is how a ty release rejecting the project's configured rule names reached main. .moon/tasks/python.yml now treats a project's own uv.lock as an implicit input, and the offending hooks bump was reverted.

💾 Backup and Restore

  • Added fetch_restore_fields(), fetch_datetime_fields(), and convert_declared_fields() to sibyl_core.backends.surreal.schema_invariants, all exported via __all__
  • content_archive.py gained _archived_record(); auth_archive.py reworked _auth_archive_record() to convert only schema-declared datetime paths
  • graph_companion_restore.py: _relationship_statements(), _mention_statements(), _episode_statements(), and _destination_projection() now return (statement, parameters) pairs; _destination_identities() validates group_id after fetch instead of inside the WHERE clause
  • source_archive_store.py: check_unique_writes() steps through probes in fixed-size chunks, and plan_source_restore() validates a keyed result across rows, states, and associations instead of a flat list
  • New coverage in apps/api/tests/test_archive_restore_raw_text.py and packages/python/sibyl-core/tests/test_restore_lookup_plans.py
  • The source revocation restore guard (apps/api/tests/test_archive_source_revocation.py) now runs against a live SurrealDB server via apps/api/moon.yml

📦 Runtime and Deployment

  • SurrealDB 4.0.0 to 4.0.1 everywhere: docker-compose.yml, docker-compose.prod.yml, docker-compose.quickstart.yml, compose.e2e.yml, .devcontainer/docker-compose.yml, charts/surrealdb (Chart.yaml appVersion and values.yaml image tag), and the Ansible role defaults
  • SURREAL_SERVER_VERSION in sibyl_core.backends.surreal.server_version is now 4.0.1, and the CLI's remediation snippets print the matching tag
  • VERSION, chart versions, and image tags move to 1.5.0-rc.2; sibyl-core pins in apps/api and apps/cli move to 1.5.0rc2
  • Deployment and install docs updated to match (docs/admin/installing.md, docs/deployment/*, docs/guide/installation.md, infra/ansible/README.md)

🔨 Release and CI Integrity

  • Homebrew formula: render_formula() dropped its python_version parameter and the generated PYTHON_PACKAGE_VERSION constant. The formula test now asserts against version.to_s, because the wheel's metadata keeps the release spelling (1.0.0-rc.1) rather than PyPI's normalized 1.0.0rc1, and that is what the CLI prints.
  • Trivy image gate now sets scanners: vuln, matching the SBOM step beside it. Without it, Trivy's secret scanner read an example credential in a third-party SDK docstring as a finding and failed the gate with CRITICALs no dependency fix could clear. A contract test holds both steps to it.
  • Contract tests no longer pin action releases by number. azure/setup-helm, aquasecurity/trivy-action, sigstore/cosign-installer, setup-node, setup-python, and download-artifact assertions now check the shape of the uses: ref (exact vMAJOR.MINOR.PATCH, or major-only where the workflow follows a major), and the AUR deploy action must still be a full commit SHA. These tests live outside what Dependabot edits, so version literals made every bump unmergeable.
  • Pre-commit ruff hook moved 0.16.4 to 0.17.0 to match the version the project runs; the stale hook re-sorted import tomllib as third-party and the project's ruff then rejected the result.
  • Collapsed two nested if statements (retrieval/reranking.py content extraction, CLI 403 remediation default) that newer ruff flags as SIM102, keeping behavior identical under both the pinned and newer linter.
  • persistence/surreal/auth_runtime/__init__.py now records what each submodule bound when a seam is patched, so deleting a propagated attribute restores the originals. pytest 9.2.0 reads a patch's old value from the target's own __dict__, and a name resolved only through __getattr__ is not there, which left fakes leaking into later tests.

🔐 Dependencies and Security

Python constraints (root pyproject.toml): dnspython >=2.9.0 to >=2.9.2 and a new soupsieve >=4.0.0 floor, both lifting transitive packages past new HIGH advisories.

Web runtime (apps/web/package.json): next 16.4.3 to 16.4.6, @tanstack/react-query 5.104.5 to 5.107.1, @tanstack/react-virtual 3.14.22 to 3.14.26, lucide-react 1.65.0 to 1.72.0, motion 14.9.0 to 14.13.0, shiki 4.5.0 to 4.6.0, next-dynenv 4.0.6 to 4.1.0, iconoir-react 7.12.1 to 7.12.2, d3-force 3.0.0 to 3.0.1.

Web dev (apps/web/package.json): vitest and @vitest/coverage-v8 5.0.5 to 5.1.0, vite 8.3.4 to 8.3.6, @vitejs/plugin-react 6.1.2 to 6.2.1, playwright 1.64.1 to 1.65.0, storybook and its addons 10.6.5 to 10.6.6, tailwindcss and @tailwindcss/postcss 4.3.3 to 4.3.5, @biomejs/biome 2.6.4 to 2.6.6.

Docs (docs/package.json): vitepress 2.0.0-alpha.20 to 2.0.0-alpha.21, mermaid 12.2.0 to 12.3.0, vue 3.5.44 to 3.5.45.

E2E (apps/e2e): playwright 1.64.1 to 1.65.1, pytest-asyncio 1.4.1.post1 to 1.5.0, ruff 0.17.4 to 0.17.5.

Actions: pnpm/action-setup 6.1.0 to 6.1.1, sigstore/cosign-installer 4.1.2 to 4.1.3.

⚠️ Breaking Changes

  • API keys can no longer approve or deny device sign-ins. Requests to POST /api/auth/device/verify authenticated with an API key are now treated as signed out and redirect with error=not_authenticated; the GET page will not identify a user from a key either. Any automation that approved device codes with a personal API key must use a signed-in session token instead.
  • sibyld db restore now exits 1 on failure. Wrappers that previously treated a partial or failed restore as success will start failing. Check the reported counts, which reflect what landed before the restore stopped.
  • SurrealDB 4.0.1 is the pinned server version. Deployments running 4.0.0 should update their image tag; the CLI and core version check expect 4.0.1.

🔧 Upgrade Notes

  • Pull the new SurrealDB image tag (v4.0.1) before upgrading Sibyl, or let the updated compose and Helm values do it. See docs/deployment/surrealdb-4-upgrade.md.
  • If you restored an archive with an rc.1 build, re-verify records whose text fields look like timestamps: those values may have been stored as datetimes. Restores taken after this release follow the destination schema.
  • Review any CI step that calls sibyld db restore and confirm it handles a nonzero exit intentionally.
  • Rotate device sign-in automation away from API keys to session tokens before upgrading.
  • Projects with their own uv.lock (hooks, apps/e2e) will see their lint and typecheck tasks rerun on the next lockfile change rather than replaying a cached result; expect a slightly longer first CI run after upgrade.

Install

Local server

curl -fsSL https://raw.githubusercontent.com/hyperb1iss/sibyl/main/install.sh | sh -s -- --version 1.5.0-rc.2

Remote CLI

curl -fsSL https://raw.githubusercontent.com/hyperb1iss/sibyl/main/install.sh | sh -s -- --remote --version 1.5.0-rc.2
sibyl init --remote https://sibyl.example.com
sibyl auth login

Homebrew

brew install hyperb1iss/tap/sibyl
sibyl up

Arch Linux (AUR)

paru -S sibyl
sibyl up

Headless server

curl -fsSL https://raw.githubusercontent.com/hyperb1iss/sibyl/main/install.sh | sh -s -- --version 1.5.0-rc.2 --no-open

Kubernetes (Helm)

helm repo add sibyl https://raw.githubusercontent.com/hyperb1iss/sibyl/gh-pages
helm repo update sibyl
helm upgrade --install sibyl sibyl/sibyl --version 1.5.0-rc.2

Artifacts

This release includes Python wheels and sdists, the generated
Homebrew formula, the generated AUR PKGBUILD, Helm charts, Docker
SBOMs, aggregate dual-registry cosign receipts, and a SHA256 checksum
manifest.