@secondlayer/cli 10.3.0 → 10.3.2

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@secondlayer/cli",
-	"version": "10.3.0",
+	"version": "10.3.2",
 	"repository": {
 		"type": "git",
 		"url": "git+https://github.com/ryanwaits/secondlayer.git",
@@ -43,7 +43,7 @@
 		"@inquirer/prompts": "^8.2.0",
 		"@secondlayer/bundler": "^0.5.0",
 		"@secondlayer/scaffold": "^1.5.1",
-		"@secondlayer/sdk": "^6.54.0",
+		"@secondlayer/sdk": "^6.54.1",
 		"@secondlayer/shared": "^7.11.1",
 		"@secondlayer/stacks": "^3.3.1",
 		"@secondlayer/subgraphs": "^3.26.4",

package/templates/subscriptions/cloudflare/README.md

@@ -23,11 +23,11 @@ https://api.cloudflare.com/client/v4/accounts/{ACCOUNT_ID}/workflows/{{NAME}}/in
 Provision the subscription with bearer auth:
 
 ```bash
-sl subscriptions create {{NAME}} --runtime cloudflare --auth-token <CF_API_TOKEN>
+secondlayer subscriptions create {{NAME}} --runtime cloudflare --auth-token <CF_API_TOKEN>
 ```
 
 You can also patch an existing subscription with
-`sl subscriptions update {{NAME}} --auth-token <CF_API_TOKEN>`.
+`secondlayer subscriptions update {{NAME}} --auth-token <CF_API_TOKEN>`.
 
 The token must have `Workflows: Edit` scope.
 

package/templates/subscriptions/node/README.md

@@ -5,8 +5,8 @@ to your business logic. No framework lock-in.
 
 ## Run
 
-`.env` is written for you at `sl subscriptions create` time with the signing
-secret already populated.
+`.env` is written for you at `secondlayer subscriptions create` time with the signing
+secret already populated. Lost it: `secondlayer subscriptions rotate-secret {{NAME}}`.
 
 ```bash
 bun install

package/templates/subscriptions/node/src/index.ts

@@ -4,8 +4,8 @@ import { Hono } from "hono";
 /**
  * Minimal Standard Webhooks receiver.
  *
- * The signing secret was shown ONCE when you ran `sl subscriptions create`.
- * If you lost it, rotate it from the dashboard: `/subscriptions/<id>` → rotate.
+ * The signing secret was shown ONCE when you ran `secondlayer subscriptions create`.
+ * If you lost it: secondlayer subscriptions rotate-secret {{NAME}}
  */
 
 const SIGNING_SECRET = process.env.SIGNING_SECRET;

package/templates/subscriptions/trigger/README.md

@@ -21,11 +21,11 @@ https://api.trigger.dev/api/v1/tasks/{{TASK_ID}}/trigger
 Provision the subscription with bearer auth:
 
 ```bash
-sl subscriptions create {{NAME}} --runtime trigger --auth-token tr_secret_abc...
+secondlayer subscriptions create {{NAME}} --runtime trigger --auth-token tr_secret_abc...
 ```
 
 You can also patch an existing subscription with
-`sl subscriptions update {{NAME}} --auth-token tr_secret_abc...`.
+`secondlayer subscriptions update {{NAME}} --auth-token tr_secret_abc...`.
 
 ## Signature verification