@muhkoo/connect 0.14.0-alpha.9 → 0.15.0-alpha.0

package/README.md

@@ -404,7 +404,7 @@ project at a time: `client.vcs.open(slug)` returns the repository for
 ```typescript
 await client.vfs.writeFile("/apps/my-app/src/index.ts", "export {};");
 const files = await client.vfs.walk("/apps/my-app");       // every file path, depth-first
-const all = await client.vfs.walkEntries("/apps/my-app");  // directories too, as VfsStat (the release after 0.14.0-alpha.8)
+const all = await client.vfs.walkEntries("/apps/my-app");  // directories too, as VfsStat (0.14.0-alpha.9)
 
 const repo = client.vcs.open("my-app");
 await repo.status();
@@ -414,7 +414,7 @@ await repo.commit("First commit");
 **Read it as untrusted input.** Hosted sign-in hands the app the master seed, so
 every app a user signs into can write any directory record, history record or
 repository object in that user's filesystem, in shapes this SDK would never
-write. From the release after 0.14.0-alpha.8, the SDK treats everything it
+write. From 0.14.0-alpha.9, the SDK treats everything it
 reads back as untrusted. A record that used to crash, hang or quietly mislead it
 now throws a typed error, or is hidden with a `[muhkoo/vfs]` warning. Two new
 errors are exported from the package root: