@elizaos/skills 2.0.3-beta.2 → 2.0.3-beta.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@elizaos/skills",
3
- "version": "2.0.3-beta.2",
3
+ "version": "2.0.3-beta.4",
4
4
  "description": "Bundled skills and skill loading utilities for elizaOS agents",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",
@@ -63,7 +63,7 @@
63
63
  "node": ">=24.0.0"
64
64
  },
65
65
  "dependencies": {
66
- "@elizaos/core": "2.0.3-beta.2",
66
+ "@elizaos/core": "2.0.3-beta.4",
67
67
  "yaml": "^2.8.2"
68
68
  },
69
69
  "devDependencies": {
@@ -73,5 +73,5 @@
73
73
  "publishConfig": {
74
74
  "access": "public"
75
75
  },
76
- "gitHead": "82fe0f44215954c2417328203f5bd6510985c1fc"
76
+ "gitHead": "f76f55793a0fb8d6b869dd8ddce03970de061e34"
77
77
  }
@@ -127,6 +127,17 @@ until the response has a usable `load_balancer_url` / `publicUrl`, then verify
127
127
  bind to `$PORT` correctly — pull `cloud.getContainerLogs(container.id, tail?)` when
128
128
  the sidecar is available and surface the logs to the human.
129
129
 
130
+ > **Two deploy surfaces — pick the right one.** `createContainer`
131
+ > (`POST /api/v1/containers`) deploys a prebuilt image you push yourself, and is
132
+ > the path this flow uses. The managed build pipeline,
133
+ > `POST /api/v1/apps/:id/deploy` (`BUILDING → READY`), is a *separate* surface
134
+ > and is **gated**: it returns `503 { code: "apps_deploy_disabled" }` unless
135
+ > `APPS_DEPLOY_ENABLED=1` on the Worker, plus a production org allowlist (`403`)
136
+ > — see `packages/cloud-api/v1/apps/[id]/deploy/route.ts`. The cloud-e2e specs
137
+ > drive the `/apps/:id/deploy` route, so a from-scratch manual test that follows
138
+ > *this* flow uses `/containers` and won't hit that gate; a tester exercising
139
+ > `/apps/:id/deploy` directly must set the flag first.
140
+
130
141
  ## 4. Set markup
131
142
 
132
143
  ```ts
@@ -17,7 +17,7 @@ The dashboard view at `https://www.elizacloud.ai/dashboard/earnings` shows the r
17
17
 
18
18
  ## Container billing
19
19
 
20
- Container hosting is pay-as-you-go, billed daily. The cron at `app/api/cron/container-billing/route.ts` runs once per day and, for each container:
20
+ Container hosting is pay-as-you-go, billed daily. The cron at `packages/cloud-api/cron/container-billing/route.ts` runs once per day and, for each container:
21
21
 
22
22
  1. Computes the day's hosting cost (CPU + RAM at the tier's per-second rate)
23
23
  2. Pulls from `redeemable_earnings_ledger` first (if `pay_as_you_go_from_earnings = true`, which is the org default)