@procedures/s3 0.1.0 → 0.2.1

package/CHANGELOG.md

@@ -1,5 +1,32 @@
 # @procedures/s3
 
+## 0.2.1
+
+### Patch Changes
+
+- Updated dependencies [a9dc8c8]
+  - @procedures/client@0.2.1
+
+## 0.2.0
+
+### Minor Changes
+
+- 76d0d64: **Breaking:** an import of a package registers nothing. The `./register` entry of a package registers its procedures, and the procedures of the modules that they need, in the global registry (ARCHITECTURE-PROPOSALS-2026-10, P9).
+  
+  - `import "@procedures/git"` gives the exports and registers nothing. Use `import "@procedures/git/register"`, or give `gitModule` (`@procedures/git/module`) to `createRegistry()`.
+  - `import "@procedures/client/register"` registers the control flow (`client.chain` and the others) and `procedure.define`/`get`/`list`/`delete`. `createRegistry()` adds them to each new registry, as before. The new `registerClientProcedures(registry?)` does the same for any registry.
+  - Each `register<Name>Procedures(registry?)` function is in the module of its package, takes a registry (the global one by default) and registers the modules that the package requires. `registerBridge` (splay) and `register` (store) are now `registerSplayProcedures` and `registerStoreProcedures`. The old names stay for one version.
+  - `sideEffects` names only `./dist/register.js`, so a bundler can drop the rest of a package.
+  - The bundles require `clientModule`, so `@procedures/bundle-mcp/register` gives the whole tool surface.
+  - `lib new` makes `src/module.ts` and a root without side effects, and `procedure new` adds procedures to the module.
+
+### Patch Changes
+
+- Updated dependencies [0cf4bea]
+- Updated dependencies [44d3e30]
+- Updated dependencies [76d0d64]
+  - @procedures/client@0.2.0
+
 ## 0.1.0
 
 The first release on npm. The packages of the client monorepo have one version together.

package/README.md

@@ -17,7 +17,7 @@ AWS S3 operations as RPC procedures. Upload, download, list, delete, and perform
 - **Zod validation**: Runtime type safety on all inputs
 - **MinIO/LocalStack support**: Custom S3 endpoints for testing
 
-The package auto-registers 9 procedures:
+The package has 9 procedures. Its register entry (`import "@procedures/s3/register"`) registers them:
 - **Standard**: `s3.upload`, `s3.download`, `s3.list`, `s3.listAll`, `s3.delete`
 - **Multipart**: `s3.multipart.init`, `s3.multipart.upload`, `s3.multipart.complete`, `s3.multipart.abort`
 
@@ -100,14 +100,10 @@ graph LR
 npm install @procedures/s3
 ```
 
-### Peer Dependencies
+Since 0.2.0, an import of the package registers nothing. To register its procedures in the global registry:
 
-```json
-{
-  "@procedures/client": "github:mark1russell7/client#main",
-  "@aws-sdk/client-s3": "^3.705.0",
-  "zod": "^3.24.0"
-}
+```ts
+import "@procedures/s3/register";
 ```
 
 ## Configuration
@@ -802,8 +798,8 @@ await client.exec(
 ```typescript
 // In bundle-data/src/register.ts
 import "@procedures/s3/register.js";
-import "@procedures/mongo"; // registers its procedures
-import "@procedures/fs"; // registers its procedures
+import "@procedures/mongo/register"; // registers its procedures
+import "@procedures/fs/register"; // registers its procedures
 ```
 
 ## Dependencies