@seta-labs/proxy 0.1.0-next.1 → 0.1.0

package/CHANGELOG.md

@@ -1,5 +1,12 @@
 # @seta-labs/proxy
 
+## 0.1.0
+
+- Promote the SDK from `0.1.0-next.1` to the ordinary `latest` npm channel.
+  The Proxy 0.13.5 HTTP contract, public SDK interfaces and runtime behavior are unchanged.
+- SDK releases publish only to npm. Consumers update their exact dependency
+  version and lockfile explicitly, then verify and release independently.
+
 ## 0.1.0-next.1
 
 ### Patch Changes

package/README.md

@@ -78,7 +78,7 @@ Supported runtime: Node.js 22+ with native Fetch, and browsers with Fetch,
 Request, Response, Headers and AbortController. TypeScript declarations are
 self-contained; the private `@seta-proxy/types` workspace is not a consumer
 dependency. The repository gate uses Node 26; tarball smoke also runs on Node 22.
-The first prerelease targets the HTTP contract of Seta Proxy `0.13.5`.
+SDK `0.1.0` targets the HTTP contract of Seta Proxy `0.13.5`.
 
 ## Packaging and release
 
@@ -90,11 +90,20 @@ checking enabled. Neither command publishes.
 Versions are independent of the application. The SDK stays on `0.x` until the
 owner explicitly authorizes graduation to `1.0`; stabilization does not imply
 that approval. Use Changesets for SDK and exposed contract changes, documenting
-compatibility and migration requirements for each `0.x` release. The prepared
-initial version is `0.1.0-next.0` (`next`). Each later release documents the minimum compatible server;
-publishing a package never deploys that server. Keep `publishConfig.tag` aligned
-when exiting prerelease mode; the workflow explicitly selects `next` or `latest`
-from the version.
+compatibility and migration requirements for each `0.x` release. Ordinary
+releases use the `latest` npm channel, without a prerelease suffix. Each later
+release documents the minimum compatible server; publishing a package never
+deploys that server or updates, merges or releases any consumer.
+
+Update explicitly from the consumer package directory:
+
+```sh
+pnpm add @seta-labs/proxy@latest --save-exact
+```
+
+`latest` selects the version at update time; the manifest records that exact
+numeric version. Commit it together with the lockfile after the consumer's
+checks pass, and release the consumer independently.
 
 The dedicated `publish-sdk.yml` accepts only `@seta-labs/proxy@<version>` tags,
 requires successful application CI on the exact tagged commit, checks tag/manifest

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@seta-labs/proxy",
-    "version": "0.1.0-next.1",
+    "version": "0.1.0",
     "description": "Typed Fetch client for the Seta Proxy application and management APIs",
     "license": "UNLICENSED",
     "type": "module",
@@ -30,7 +30,7 @@
     ],
     "publishConfig": {
         "access": "public",
-        "tag": "next",
+        "tag": "latest",
         "provenance": false
     },
     "scripts": {