chore: prepare 0.8.23 release - #482
Draft
leehack wants to merge 4 commits into
Draft
Conversation
Contributor
|
Chat app preview deployed for
|
This was referenced Sep 7, 2026
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.
Summary
Refreshed at
041e35b6ffc7dbe7dcc4a7722c3043044f1c2ffbagainstdee010e24f95a50f71830116087af6db3c6c7640: merged #486 is integrated normally, with exact-head CAS protection and no force-push. The eight-file release diff and all runtime pins remain unchanged. Fresh independent Astra review, all local gates and all 15 exact-head hosted checks pass. Draft remains held only for explicit release approval.Prerequisite corrective PR #484 merged at
ccc2d35633e3ca6347a697f19fde4944e0a8dbd0, closing P1 #483, and is integrated here by a normal merge without force-push.Apple upgrade behavior: existing app constraints
llamadart: ^0.8.22with Apple companion^0.0.17can still resolve the new core patch while excluding companion0.0.18. The merged hook now verifies the actual resolved companion and maintained SwiftPM runtime manifest before symbol lookup. That mismatched pair fails the build with actionable upgrade guidance; it cannot silently link the old v0.3.0 framework to v0.4.0 bindings. Consumers must update the companion constraint to^0.0.18alongside core^0.8.23. The guard does not rewrite app constraints.0.8.23with already-integrated nativev0.4.0and Web assetsv0.1.43; no runtime pin, binding, or implementation changes in this PR.0.0.18, retain LiteRT companion0.0.10, and replace temporary development overrides with compatible package installation snippets.0.8.23and disclose the known upstream grammar boundary limitation.Production-readiness scope
This is a draft release-prep PR, not a publication action. Merging this versioned release-prep branch authorizes automatic companion-first publication and the core release, so it must not merge until the maintainer explicitly approves release.
0.8.23llamadart-native@v0.4.0, upstream5266f24da75dc449bd56cbed7addb9c8e4a6a73e0.0.18, already prepared on mainv0.1.43, manifest111eefc3588842cebfe665b363378edca34924764610263e1eda5280dfcfaa27v0.16.0-native.2/0.0.10, unchanged@litert-lm/core@0.15.0, unchangedThe root-path chat example lock was regenerated by canonical pub resolution and changes only the core package version. Historical release docs are untouched. Core
0.8.22must remain paired with Apple companion0.0.17; the new pair is core0.8.23+ companion0.0.18.Known limitations and independent follow-ups
root ::= "a"{2000}at grammar sampler initialization;{1999}succeeds. The raw upstream fix is independent qualification work and is not included or mislabeled as a wrapper rebuild here.756f4d3c4d020e2de4e26b029ebe9aad26073b4f14c425ce76d10e1c6922a73f; full selectedandroid_armv9.0_1, compactandroid_armv8.0_1. Device sourcef43ada361ccde89ca1d2a0b57c10db87691b5a91predates the Apple-only prebuild guard and release/docs changes; native artifact and generation code are unchanged. A disclosed six-line logging overlay identified the selected module without changing selection/inference; it was removed, and the original installed APK was restored without clearing user data. Independent Astra artifact/log/restoration audit passed. Durable evidence:/private/tmp/llamadart-pixel-0907/handoff.mdandindependent-astra-audit.md.Validation
3.47.1/ Dart3.13.1workspace preparation, whole-workspace format and analysis.verify_release_docs_versions.dart --release-prep(core0.8.23, Apple0.0.18, LiteRT0.0.10, nativev0.4.0).dart pub publish --dry-run, 0 warnings, no publication.0.0.18currently returns 404; LiteRT companion0.0.10returns 200. The existing post-merge workflow must publish Apple0.0.18before tagging the core; no publication was performed for this draft.95e76865fb444f3187da47398cfab03a0af3ad46da6a9026e1d490401401355a), without changing defaults or setting a local runtime override.Review gates
high-risk / artifactConsumer(package/release metadata); release and high-risk matrix rows were inventoried. Production runtime/consumer implementation is unchanged; branch-deletion testing is N/A to this version/docs-only diff. Existing release-doc companion-pin regressions passed within the full VM suite.041e35b6ffc7dbe7dcc4a7722c3043044f1c2ffb; current basedee010e24f95a50f71830116087af6db3c6c7640.unverifiedPrerequisites/externalPrerequisitesUnavailable/ exit 2: repository-local evidence is internally consistent, not authenticated operational attestation. As documented indoc/high_risk_pre_merge_readiness.md, external App/auditor/environment/ruleset enforcement is intentionally unconfigured and is not a pending merge requirement. Current readiness uses manual repository-local review and evidence. Adopting external enforcement would require a separately approved governance project; this release does not request or configure it.