Repository navigation
chore(release): v0.3.0-preview.144 - #554
Merged
Merged
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release prep for Host
0.3.0-preview.144fromorigin/masterat377ae46e.0.3.0-preview.144inpackage.json, theDEFT_RELEASE_VERSIONfallback (apps/api/src/lib/agent-channel.ts) andintegrations/hermes/integration-manifest.json. Schema head stays0.3.0-preview.149(already on master; matches the upgrade manifest).core(unchanged inrelease/release-scope.json). Author Kit stays0.1.0-alpha.43; its source is unchanged sincev0.3.0-preview.143.CHANGELOG.md: candidate notes under[Unreleased], marked publication pending, covering the 23 pull requests merged sincev0.3.0-preview.143(fix(agent): report approval outcomes, order replies, and sign native actions #529–fix(deps): update Next.js to 16.4.6 to clear the root params advisory #540, fix(security): trust proxy peers for general rate limits #542–fix(privacy): keep customer content out of API and worker logs #549, feat(paused): tell people why a paused workspace is read-only #551–fix(apps): key Apps rate limiters on the trusted client address #553). The upgrade notes coverpnpm db:upgrade(ledger entries.144,.148,.149),DEFT_INVITE_TRUSTED_PROXIESfor all address-based rate limits, new and stricter settings (DEFT_HOSTED,DEFT_PAUSED_START,DEFT_PAUSED_REASON, the hosted-only settings), owner-only management of admins, heartbeat prompt references,/health/ready, and content-free logs.Local checks:
release-source-identity,hermes-release, the app-kitpackage-versiontest,resolve-release-scope(core),check:add-only-upgrades,docs:checkand the API typecheck all pass.Still to do:
v0.3.0-preview.144from the merge commit once its checks are green.author-kit-release.json. Confirm there are no Hermes artifacts orhermes_*claims (core scope). Then run the Cosign and attestation verification.[Unreleased]and update the comparison links. Also move the install pins and the "latest published" statements to 144. README, FEATURES, ROADMAP and docs still namev0.3.0-preview.142because no follow-up PR was made for 143.🤖 Generated with Claude Code