@zhiman_innies/innies-codex 0.122.50 → 0.122.51

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.
@@ -492,11 +492,16 @@ function normalizeManagedProviderBlocks(contents) {
492
492
  // NOTE: we deliberately do NOT auto-inject `base_url` or `env_key`
493
493
  // into user blocks. The user must configure these themselves (either
494
494
  // in the TOML block or via the corresponding env var: ZHIMAN_API_KEY
495
- // / DASHSCOPE_API_KEY / ZHIMAN_35B_API_KEY). The Rust builtin
496
- // providers fall back to the env var when `env_key` is absent from
497
- // the TOML, so the only thing that is strictly required from the
498
- // user is `base_url` (or the ZHIMAN_BASE_URL / DASHSCOPE_BASE_URL env
499
- // var). We only normalize `wire_api` to a known-good value.
495
+ // / DASHSCOPE_API_KEY). The Rust builtin providers fall back to the
496
+ // env var when `env_key` is absent from the TOML, so the only thing
497
+ // that is strictly required from the user is `base_url` (or the
498
+ // ZHIMAN_BASE_URL / DASHSCOPE_BASE_URL env var). We only normalize
499
+ // `wire_api` to a known-good value. (Historically the comment also
500
+ // mentioned `ZHIMAN_35B_API_KEY`, but the Rust factory at
501
+ // `codex-rs/model-provider-info/src/lib.rs` hardcodes a single
502
+ // `ZHIMAN_API_KEY` env-var name for ALL `zhiman_*` provider blocks —
503
+ // there is no per-model differentiation. Users who need separate
504
+ // env vars must override `env_key` in the TOML block directly.)
500
505
  let updated = normalizeProviderBlock(contents, {
501
506
  providerHeader: ZHIMAN_35B_PROVIDER_HEADER,
502
507
  });
@@ -614,17 +619,26 @@ function defaultZhiman35bProviderBlock() {
614
619
  // `base_url` or `env_key`. The user must configure both:
615
620
  //
616
621
  // base_url = "http://your-private-deployment/v1"
617
- // env_key = "ZHIMAN_35B_API_KEY" # or any other env var name
622
+ // env_key = "ZHIMAN_API_KEY" # or any other env var name
618
623
  //
619
- // (or set the ZHIMAN_BASE_URL and ZHIMAN_35B_API_KEY environment
624
+ // (or set the ZHIMAN_BASE_URL and ZHIMAN_API_KEY environment
620
625
  // variables). Generating a default `base_url` here would make the
621
626
  // binary call a real network endpoint on first run, which is
622
627
  // explicitly disallowed by the innies-codex install contract.
628
+ //
629
+ // NOTE: the env-var name is `ZHIMAN_API_KEY` (NOT `ZHIMAN_35B_API_KEY`)
630
+ // because the Rust builtin factory at
631
+ // `codex-rs/model-provider-info/src/lib.rs` hardcodes that single
632
+ // env-var name for ALL `zhiman_*` provider blocks — there is no
633
+ // per-model env-var differentiation. If you need different keys for
634
+ // the 27B vs 35B deployments, override `env_key` in the TOML block
635
+ // directly (e.g. `env_key = "ZHIMAN_35B_API_KEY"`) instead of relying
636
+ // on the factory default.
623
637
  return [
624
638
  ZHIMAN_35B_PROVIDER_HEADER,
625
639
  'name = "zhiman_35b"',
626
640
  `# base_url = "http://your-private-deployment/v1" # FILL IN: private vLLM / OpenAI-compatible endpoint`,
627
- `# env_key = "ZHIMAN_35B_API_KEY" # FILL IN: name of the env var holding your API key`,
641
+ `# env_key = "ZHIMAN_API_KEY" # FILL IN: name of the env var holding your API key`,
628
642
  `wire_api = "${DEFAULT_PROVIDER_WIRE_API}"`,
629
643
  ].join("\n");
630
644
  }
@@ -634,13 +648,16 @@ function defaultZhiman27bProviderBlock() {
634
648
  // deployment. Same install-contract rule: do NOT prefill `base_url` or
635
649
  // `env_key` — the user must configure both, otherwise the binary
636
650
  // would call a real network endpoint on first run. Distinct provider
637
- // name (`zhiman_27b` vs `zhiman_35b`) and env var so the two private
638
- // deployments can be configured independently.
651
+ // name (`zhiman_27b` vs `zhiman_35b`) so the two private deployments
652
+ // can be configured independently. NOTE: the env-var name is still
653
+ // `ZHIMAN_API_KEY` (NOT `ZHIMAN_27B_API_KEY`) because the factory
654
+ // hardcodes that single name for ALL zhiman_* blocks — see the
655
+ // matching note in `defaultZhiman35bProviderBlock`.
639
656
  return [
640
657
  ZHIMAN_27B_PROVIDER_HEADER,
641
658
  'name = "zhiman_27b"',
642
659
  `# base_url = "http://your-private-deployment/v1" # FILL IN: private vLLM / OpenAI-compatible endpoint`,
643
- `# env_key = "ZHIMAN_27B_API_KEY" # FILL IN: name of the env var holding your API key`,
660
+ `# env_key = "ZHIMAN_API_KEY" # FILL IN: name of the env var holding your API key`,
644
661
  `wire_api = "${DEFAULT_PROVIDER_WIRE_API}"`,
645
662
  ].join("\n");
646
663
  }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@zhiman_innies/innies-codex",
3
- "version": "0.122.50",
3
+ "version": "0.122.51",
4
4
  "license": "Apache-2.0",
5
5
  "bin": {
6
6
  "innies": "bin/innies.js"
@@ -23,9 +23,9 @@
23
23
  "postinstall": "node bin/innies-init.js"
24
24
  },
25
25
  "optionalDependencies": {
26
- "@zhiman_innies/innies-codex-darwin-x64": "0.122.50-darwin-x64",
27
- "@zhiman_innies/innies-codex-darwin-arm64": "0.122.50-darwin-arm64",
28
- "@zhiman_innies/innies-codex-win32-x64": "0.122.50-win32-x64",
29
- "@zhiman_innies/innies-codex-win32-arm64": "0.122.50-win32-arm64"
26
+ "@zhiman_innies/innies-codex-darwin-x64": "0.122.51-darwin-x64",
27
+ "@zhiman_innies/innies-codex-darwin-arm64": "0.122.51-darwin-arm64",
28
+ "@zhiman_innies/innies-codex-win32-x64": "0.122.51-win32-x64",
29
+ "@zhiman_innies/innies-codex-win32-arm64": "0.122.51-win32-arm64"
30
30
  }
31
31
  }