Skip to content

v1.1.5

Choose a tag to compare

@github-actions github-actions released this 26 Jul 00:29
· 564 commits to main since this release

Release Notes v1.1.5

Released: 2026-07-26

This release closes a supply-chain gap in the release pipeline that let a HIGH-severity postcss advisory reach two tagged builds, and rebuilds the release workflow so the code Nightly Regression validated is provably the code that gets tagged. It also corrects the distilled-note retrieval reservation to a fixed slot count after a widening regression, and retires the legacy-term inventory scanner in favor of a leaner runtime purity guard.

Highlights

🔒 Scan images before any tag is pullable

The docker-security job in .github/workflows/publish.yml now scans the untagged digests that docker-build pushed, running before docker-merge publishes a tag. A HIGH or CRITICAL CVE stops the release before anything is public and immutable. Previously the scan ran after the merge, which left two releases half-shipped: the image was already pullable while only signing and Helm were withheld. Every architecture (amd64, arm64) is now scanned by digest rather than the merged manifest.

🐛 Block shipped-dependency CVEs at review time

A new dependency-audit job in .github/workflows/ci.yml runs pnpm audit --prod --audit-level=high on every change, so a shipped CVE fails a merge instead of surfacing only mid-release. Scope is --prod, so dev-only advisories in Storybook or VitePress never block. A KNOWN_ADVISORIES allowlist accepts tracked debt and may only shrink; it currently ships empty because the advisory this gate was built for is now fixed.

🔒 Raise the postcss floor past the advisory

The postcss override in pnpm-workspace.yaml moves from ^8.5.15 to ^8.5.18, clearing the path-traversal advisory that motivated the new audit gates. python publishing to PyPI now also waits on docker-security, so a CVE cannot leave an unrecallable version number behind.

♻️ Workflow-owned version bump with a same-SHA proof

The Release workflow in .github/workflows/release.yml now applies the version bump itself instead of demanding a hand-committed release candidate. It runs moon run sync-versions, then proves the bump touched nothing but generated pins by diffing git status --porcelain against tools/release/sync_versions.py --list-targets. Pins are staged by name (never git add --all), and a second step re-validates the committed bump against the recorded base SHA. The Nightly Regression run ID is now auto-resolved from that base SHA when not supplied.

⚡ Pin the distilled-note lane to an absolute slot count

compose_operational_evidence in sibyl_core/retrieval/operational_evidence.py now reserves a fixed TYPED_NOTE_RESERVATION_ITEMS = 3 slots for independently ranked notes rather than ceil(limit * 3/8). A slice-granular pack raises limit from 8 to ~28 for reasons unrelated to note count; the proportional reservation widened the lane from 3 to 5 and lost the entire measured note gain (-3.70pp/domain). Small packs still shrink the reservation so it never consumes the whole pack.

CI and Release Pipeline

  • docker-security scans by immutable digest (@sha256:...) with a per-platform matrix and emits per-platform SBOMs; docker-sign now depends on docker-merge, and docker-merge depends on docker-security.
  • python publish gate: needs: [rc-gate, docker-security] with an if guard that still allows dry runs (the scan is skipped, not passed).
  • The dependency audit ratchets on known advisories instead of blocking on existing debt, so accepted debt is visible without stalling merges.
  • Nightly Regression run resolution: the workflow queries gh run list for a successful run on the base SHA and fails with an actionable message when none exists.

Retrieval

  • compose_operational_evidence gains a typed_reservation_items parameter defaulting to the new module constant, and exports TYPED_NOTE_RESERVATION_ITEMS. The docstring now states the reservation is absolute, not proportional.

Tooling and Inventory

  • tools/inventory/runtime_surface.py drops the entire legacy-term scanner: the regex, scan roots, allowlist records, and the --check snapshot comparison. A new check_runtime_purity guard fails on SQLModel tables, raw SQL, session storage, or legacy dependencies outside the now-frozen ALLOWED_LEGACY_DEPENDENCIES allowlist. The tool's purpose shifts from snapshot generation to guarding the runtime against the legacy stack, with markdown reporting available on demand.
  • tools/release/sync_versions.py adds --list-targets, printing every path a bump may touch so the Release workflow can prove its bump commit contains only pins.
  • The retired inventory snapshot moves to docs/_archive/RUST_PORT_INVENTORY_2026-07.md; docs/research/rust-port/INVENTORY.md is deleted.

Dependencies and Config

  • apps/web/biome.json schema pin raised from 2.5.0 to 2.5.3 to match the pinned binary.
  • Version pins across apps/api/pyproject.toml, apps/cli/pyproject.toml, charts/sibyl/Chart.yaml, charts/surrealdb/Chart.yaml, compose files, and Ansible defaults advance to 1.1.5.

Documentation

  • Deployment and install guides (docs/cli/docker.md, docs/deployment/*.md, docs/guide/installation.md) updated alongside the version bump.

Breaking Changes

  • runtime_surface.py --check no longer verifies a committed snapshot. The legacy-term inventory and snapshot comparison are removed. --check now runs the Graphiti-exit and runtime-purity guards. Any process expecting the old snapshot diff behavior, or the LegacyTermRecord / LEGACY_TERM_ALLOWLIST symbols, must migrate to the purity guards.
  • Release dispatch no longer requires a pre-committed VERSION. The workflow bumps and commits the version itself. Adjust any runbook that expected to hand-commit a release candidate before dispatch; nightly_run_id is now optional and auto-resolved from the base SHA.

Upgrade Notes

  • Regenerate lockfiles if you pin postcss locally; the workspace floor is now ^8.5.18.
  • If you consume runtime_surface.py in tooling, switch from snapshot checks to check_runtime_purity and the frozen ALLOWED_LEGACY_DEPENDENCIES allowlist.
  • Callers of compose_operational_evidence that relied on a proportional note reservation should confirm the fixed 3-slot default fits their pack sizes, or pass typed_reservation_items explicitly.
  • Update release runbooks to drop the manual VERSION commit step and to rely on auto-resolution of the Nightly Regression run.

Install

Local server

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

Remote CLI

curl -fsSL https://raw.githubusercontent.com/hyperb1iss/sibyl/main/install.sh | sh -s -- --remote --version 1.1.5
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.1.5 --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.1.5

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.