Skip to content

chore(release): v0.3.0-preview.144 - #554

Merged
Maneek21 merged 3 commits into
masterfrom
chore/release-0.3.0-preview.144
Nov 19, 2026
Merged

Maneek21 merged 3 commits into
masterfrom
chore/release-0.3.0-preview.144

Conversation

@Maneek21

Copy link
Copy Markdown
Owner

Release prep for Host 0.3.0-preview.144 from origin/master at 377ae46e.

Local checks: release-source-identity, hermes-release, the app-kit package-version test, resolve-release-scope (core), check:add-only-upgrades, docs:check and the API typecheck all pass.

Still to do:

  • Merge on green CI, including Dependency Review.
  • Push the annotated tag v0.3.0-preview.144 from the merge commit once its checks are green.
  • Check the release workflow's assets: LICENSE, NOTICE, THIRD-PARTY-LICENSES.md, default.env.example, source archive, SBOM, SHA256SUMS, compose files, self-hosting.md, Kit tarball and author-kit-release.json. Confirm there are no Hermes artifacts or hermes_* claims (core scope). Then run the Cosign and attestation verification.
  • Follow-up docs PR: file the notes as a dated section, add an empty [Unreleased] and update the comparison links. Also move the install pins and the "latest published" statements to 144. README, FEATURES, ROADMAP and docs still name v0.3.0-preview.142 because no follow-up PR was made for 143.

🤖 Generated with Claude Code

Maneek21 and others added 3 commits November 19, 2026 16:16
Set the Host version to 0.3.0-preview.144 in package.json, the
DEFT_RELEASE_VERSION fallback and the Hermes integration manifest.
Release scope stays core; Author Kit stays 0.1.0-alpha.43.

CHANGELOG: candidate notes for the changes merged since
v0.3.0-preview.143, under [Unreleased] and marked publication pending,
with upgrade notes (schema .144/.148/.149, trusted proxies, new and
stricter settings, owner-only admin management, heartbeat prompts,
health and logs).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…s and a paused start

Review of the release-prep change found two wrong statements and three
places that needed tightening:

- database error details are not logged (changed by #549); the note said
  they were logged under the reference id
- install instructions are pinned to the published 142 release, not to
  "the latest published release"
- readiness failure responses and the removal of dead push subscriptions
  already shipped in 143; only `paused` reporting is new
- the picomatch advisory was withdrawn by GitHub on 18 November 2026

docs/self-hosting.md ships as a release asset, so the new settings and the
readiness rule go in before the tag: DEFT_PAUSED_START, DEFT_PAUSED_REASON,
the hosted-only settings to leave unset, and "route traffic only when
/health/ready returns 200 and paused is false".

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…start refuses

Three wording points from the re-check of the release-prep change:

- /health/ready checks the database query, the agent-channel claim and lease
  columns, the wiki_memory_syncs table and job-worker startup; it does not
  compare the upgrade ledger with schema_head
- a paused install reports paused on both endpoints, but /health/ready still
  answers 503 until its normal checks pass
- sign-in while paused includes two-step verification and required enrolment;
  the static agent-channel contract stays readable; reads that change shared
  state are refused

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@Maneek21
Maneek21 merged commit ee3f86d into master Nov 19, 2026
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant