Repository navigation
Prepare v0.1.0-beta.149 - #1092
Merged
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.
Prepare the reserved
0.1.0-beta.149release withpnpm version:set. The Connect cohort, SDK manifest/npm lock and Obsidian SDK peer/local lock agree on that exact version. The generator assembles the pending notes, refreshes architecture counters and consumes changelog/growth fragments, including second-computer approval (#982), daemon credential-store retry (#1086), and enforced tag/asset integrity (#1091).The candidate includes main
f531326198d64a7e5658730db91d43b619037958. The later daemon-only change and integrity documentation leave the application WASM inputs unchanged frome161f426a521c39adf8ca057255fa940338f7de4. Refresh the SDK application WASM pin from those inputs using Rust 1.94.0, locked Binaryen and the publication workflow's canonical path remaps: 3,720,400 bytes, SHA-256643eef6203bc7d394c76f9e305faa8977ea97785758b9cb076efda05d4f4d83f. Regenerate the native method inventory and update its packaged-asset expectation and documentation. This addresses the stale-pin failure in SDK build run 41126172862; the new CI source build must independently reproduce the digest.Replace a 5 ms abort in the pending-setup test with an observed native pending poll. The original timer could abort before a review existed, making its cancel assertion race with setup. Cancellation still must reject, send cancel, issue no apply and retain no mutation ID; production code is unchanged by this test fix.
Main carried consistent beta.147 metadata after the runtime import; this advances directly to the reserved beta.149. Deployed beta.148 remains the predecessor. Production trust remains the exact beta.141 asset (840 bytes; SHA-256
7912e40838213e60b65848350d319a48019021317b112e3326429b250f0133d7). Publication remains tag-gated and requires independent production verification. There are no Worker, trust, policy-key or migration changes, and no waivers.Validation:
pnpm ci:local --node, including remote builds/typechecks/tests and package audit, passed.95f6f36d5f0de87ec03be5a5045a84f25fc8229b. No root Rust source changed during this refresh; PR and exact-merge CI remain required.All PR workflows must pass before this candidate enters the normal merge queue. Passing the single required Qualification check alone does not establish SDK, Runtime or Desktop qualification. No tag, deployment or publication has occurred.