relaymessenger 0.1.18-staging.0 → 0.1.18

package/README.md

@@ -5,7 +5,7 @@ v1 Agent API. It delegates all Relay calls and response types to
 `@relaymessenger/sdk`.
 
 Source is maintained in
-[`RelayMessenger/Relay-SDK`](https://github.com/RelayMessenger/Relay-SDK/tree/staging/packages/cli)
+[`RelayMessenger/Relay-SDK`](https://github.com/RelayMessenger/Relay-SDK/tree/main/packages/cli)
 under `packages/cli`.
 
 ## Selection
@@ -83,7 +83,7 @@ installation; cancelling stops setup before any identity is created. Accepting r
 agents and project/global scope:
 
 ```sh
-npx --yes skills@1.5.25 add https://github.com/RelayMessenger/Relay-SDK/tree/staging/skills/relay --skill relay
+npx --yes skills@1.5.25 add https://github.com/RelayMessenger/Relay-SDK/tree/main/skills/relay --skill relay
 ```
 
 The CLI does not silently download skills or change every agent's configuration.
@@ -171,7 +171,7 @@ the way `gh auth token` does. Use it to give the token to the SDK:
 
 ```sh
 export RELAY_AGENT_TOKEN=$(relay auth token)
-relay auth token --profile staging
+relay auth token --profile work
 ```
 
 Profiles live in `${XDG_CONFIG_HOME:-~/.config}/relay/config.json`. The
@@ -301,8 +301,7 @@ credential by its authenticated Contact Card, refusing unavailable or ambiguous
 matches (including the same handle on multiple origins). It only clears that
 profile's matching saved token after Relay confirms the agent is gone. If Relay
 errors, or does not answer, the saved token stays; tokens for other profiles and
-for your environment are never touched. New creation defaults to the staging API when this package has a staging prerelease
-version; it never inherits an empty legacy production profile. Explicit `--api-url`
+for your environment are never touched. New creation defaults to `https://api.relayapp.im`; it never inherits an empty legacy production profile. Explicit `--api-url`
 or `RELAY_API_URL` overrides remain authoritative, and existing profile origins
 are unchanged. Creation is never automatically retried. If creation succeeds but local
 storage fails, the command reports the safely assigned handle and whether local
@@ -442,25 +441,16 @@ npm run validate
 operation-hash check, boundary checks, package packing, isolated tarball
 installation, and installed-bin doctor smoke tests.
 
-## Staging
+## Profiles
 
-Install `relaymessenger@staging` to work against the staging environment:
+An explicit `--api-url` or `RELAY_API_URL` always wins over the default origin,
+for example:
 
 ```sh
-npx relaymessenger@staging --version
-npm install --global relaymessenger@staging
-```
-
-That build talks to `https://api.staging.relayapp.im` on its own and installs
-the Relay skill from the repository's `staging` branch; a plain `relaymessenger`
-build talks to `https://api.relayapp.im` and installs from `main`. Either way an
-explicit `--api-url` or `RELAY_API_URL` still wins, for example:
-
-```sh
-relay profiles add staging --api-url https://api.staging.relayapp.im
-relay profiles use staging
-printf '%s' "$STAGING_RELAY_AGENT_TOKEN" |
-  relay auth login --profile staging --with-token
+relay profiles add work --api-url https://api.relayapp.im
+relay profiles use work
+printf '%s' "$RELAY_AGENT_TOKEN" |
+  relay auth login --profile work --with-token
 relay profiles list
 ```
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "relaymessenger",
-  "version": "0.1.18-staging.0",
+  "version": "0.1.18",
   "description": "Official command-line client for Relay v1 resources.",
   "type": "module",
   "bin": {
@@ -31,8 +31,8 @@
     "@agentclientprotocol/sdk": "1.4.0",
     "@anthropic-ai/claude-agent-sdk": "0.3.278",
     "@clack/prompts": "1.8.1",
-    "@relaymessenger/pi": "0.1.7-staging.0",
-    "@relaymessenger/sdk": "0.5.1-staging.0",
+    "@relaymessenger/pi": "0.1.7",
+    "@relaymessenger/sdk": "0.5.1",
     "@vercel/detect-agent": "1.2.5",
     "commander": "^15.0.0",
     "smol-toml": "^1.8.0",