chore(release): prepare v0.3.0-preview.15 core preview - #319
Merged
Conversation
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.
This prepares the next core preview from the fixes already accepted on the demo. It includes durable sessions and credential revocation, safe native-create retries, note recovery, calendar and attachment fixes, App authority checks, and backup/process recovery. Production runtime source matches the accepted demo apart from the release-version fallback.
The release contract now selects
coreexplicitly. It retains security, image, upgrade, and bundle regression gates while making no Hermes runtime certification claim. Existing installations must use the backup-first upgrade path through schema preview.29.Public guidance distinguishes published preview.14, the upcoming preview.15 candidate, experimental Apps, and planned capabilities. It separates personal MCP permissions from governed employee actions, documents the required App flags and keyrings, and supplies matching authoring versions and setup paths. Candidate notes remain visibly unreleased until publication.
The automation lifecycle test now configures its required flags before imports and supplies matching database-complete test keyrings to the production runtime. The setup is isolated to that test process; production defaults and lifecycle assertions are unchanged.
Validation:
57a6ba7c08581203e5d329217f377fd4bf6c2108passed Type Check, Test API, Build, Versioned Upgrade, Production Image + Browser Smoke, CodeQL, Dependency Audit, and Dependency Review. API: 1,352 passed, zero failed, 12 skipped. The Linux signal check passed. Hermes certification is intentionally excluded by core scope.The mobile Apps fix in #317 and Tiptap dependency update in #318 are included. Website changes are staged separately; this PR does not deploy the website or publish a release.