Repository navigation
Release v0.3.0 with connected-folder and sandbox verification - #15
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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 v0.3.0 so the installer ships the connected-folder client and environment-based startup already merged on main. Update the CLI/WASM version, website labels, setup guidance, and release instructions.
Expand the managed connected-folder check to pair from the current directory, exercise both read-only and writable modes, edit a file and read it back from disk, and revoke access. Add an opt-in live Vercel sandbox check covering real file I/O, native Node execution, and shared browser-protocol/native-terminal turns. Both automated checks use scripted model responses.
Validation:
cargo test --locked, optimized CLI build, 13 installer tests, release smoke check, and setup PTY checks passed.--root, wrote and read back a file from the browser, appended a line from the terminal, verified both on disk and in the browser, and recovered the transcript after reload.After merge, publish tag
v0.3.0, wait for all four platform builds, then verify the production installer and downloaded artifacts.