Repository navigation
Prepare remote-first 0.1.7 release and fix verified API scenarios - #73
Merged
Merged
Conversation
rdlabo
marked this pull request as ready for review
October 26, 2026 08:55
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.
Existing API tests missed input-view, callback, stream lifetime and constructor behavior. This change adds 18 reviewed operation mappings and shared Workers comparisons, and fixes ECDH view access, key-length getter evaluation, vector I/O extents, FileHandle BYOB cleanup, and Stats constructor identity.
Release acceptance now follows the maintainer-approved remote-first application policy: existing Workers apps must build and work through their deployed Worker. Whole-module Complete remains a separate criterion. Unimplemented APIs, unverified behavior, Better Auth origin restrictions and unsupported upgrades remain documented. Onboarding targets matching npm, SwiftPM and Maven 0.1.7 dependencies; distribution must be verified before release completion.
New regressions verify that remote-only server dependencies need not resolve or evaluate in the client, and failed remote mutations are neither retried nor executed locally. The test guide maps release contracts to the existing package, framework, native transport and embedding suites.
Validation:
The source index covers 70 modules / 1,597 export slots as navigation candidates, not behavioral certification. Only the 18 named operation mappings were reviewed; missing APIs and whole-module work remain In progress. Logs, failed attempts, hashes and reviews are retained in artifacts/validation/existing-api-coverage. The runtime-validated tarball SHA-256 is 25704ac7b24b42d15e9359996f56add332abe5665f7486b89f053b5497c31d48; final release packaging is performed by CI.