@singularity-layer/cli 0.3.0 → 0.4.0

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/dist/cli.js CHANGED
@@ -1082,7 +1082,7 @@ async function followLogs(base, slug, creds, limit) {
1082
1082
  }
1083
1083
 
1084
1084
  // src/version.ts
1085
- var VERSION = "0.3.0";
1085
+ var VERSION = "0.4.0";
1086
1086
 
1087
1087
  // src/cli.ts
1088
1088
  var COMMANDS = {
@@ -1101,9 +1101,13 @@ ${Object.entries(COMMANDS).map(([k, v]) => ` ${k.padEnd(14)} ${v.blurb}`).join(
1101
1101
  SGL_API_KEY=x402c_... authenticate with a compute API key instead of a keypair.
1102
1102
  Prefer the env var: --api-key <key> works too, but argv is
1103
1103
  visible in ps and your shell history. Needs processors:write
1104
- (processors:read for read-only commands). Cannot deploy unless
1105
- the key's wallet is a Solana one, since that address becomes
1106
- your payout account, and 'run' uses the invoke-token lane.
1104
+ (processors:read for read-only commands). A key from a Solana
1105
+ wallet deploys as that wallet. A key from a Google/GitHub/X login
1106
+ (an ACCOUNT key) deploys processors owned by the account: the
1107
+ manifest must set "payout": { "solana": "<a Solana wallet linked to
1108
+ your account>" }, and that payout cannot be changed afterwards.
1109
+ Account keys cannot change a linked wallet's processors (that
1110
+ needs the wallet). 'run' uses the invoke-token lane.
1107
1111
  --json machine-readable output, for scripts and agents
1108
1112
 
1109
1113
  Other Singularity CLIs, deliberately separate:
@@ -1126,7 +1130,7 @@ async function main() {
1126
1130
  const res = await api(resolveBase(flags), "GET", "/processors", { ...creds });
1127
1131
  const owner = res.owner || "";
1128
1132
  if (!owner) die("the API key is valid but returned no owner wallet");
1129
- const chain = owner.startsWith("0x") ? "evm" : "solana";
1133
+ const chain = owner.startsWith("acct:") ? "account" : owner.startsWith("0x") ? "evm" : "solana";
1130
1134
  ok(flags.json ? JSON.stringify({ address: owner, chain, via: "api-key" }) : owner);
1131
1135
  return;
1132
1136
  }
package/dist/index.js CHANGED
@@ -301,7 +301,7 @@ function coerce(raw, type) {
301
301
  }
302
302
 
303
303
  // src/version.ts
304
- var VERSION = "0.3.0";
304
+ var VERSION = "0.4.0";
305
305
  export {
306
306
  MAX_BUNDLE_BYTES,
307
307
  VERSION,
package/dist/version.d.ts CHANGED
@@ -8,4 +8,4 @@
8
8
  *
9
9
  * Kept in sync with package.json by the release workflow, which is the only thing that bumps either.
10
10
  */
11
- export declare const VERSION = "0.3.0";
11
+ export declare const VERSION = "0.4.0";
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@singularity-layer/cli",
3
- "version": "0.3.0",
3
+ "version": "0.4.0",
4
4
  "description": "Singularity developer CLI \u2014 deploy paid endpoints (Processors) on the Singularity Cloud Network",
5
5
  "type": "module",
6
6
  "bin": {