Skip to content

release: 0.3.5 — router-core 3aca0e1 (Gemini 4 Argon capabilities) - #36

Closed
VickyXAI wants to merge 1 commit into
mainfrom
chore/router-core-3aca0e1
Closed

VickyXAI wants to merge 1 commit into
mainfrom
chore/router-core-3aca0e1

Conversation

@VickyXAI

Copy link
Copy Markdown
Contributor

Pins @blockrun/router-core 2cd5a10 → 3aca0e1 (router-core #9).

Routing unchanged:

  • router-core's 88-request decisions.snapshot.json is byte-identical between 2cd5a10 and 3aca0e1, and portfolio.ts / chains are untouched.
  • The only added content is a google/gemini-4-argon capability entry with supportsTools: false, so it fails closed for tool requests.
  • router-core chore(brand): refresh the snapshot — the markers were rendering a stale catalog #10, which adds tool-chain fallbacks and changes fallback lists, is deliberately not included.
  • The lockfile diff is limited to the router-core resolved / integrity / dependency lines, and npm ci accepts it.

Also releases #33 (Mistral Large 4 at $1.36/$4.18), which merged after the last release without a version bump.

Tests: npm test passes 395/395.

Pins @blockrun/router-core 2cd5a10 -> 3aca0e1 (router-core #9): one added
capability entry, google/gemini-4-argon, supportsTools false (fails closed).
router-core's decisions.snapshot.json is byte-identical across that range;
router-core #10 (new tool-chain fallbacks) is not picked up.

Also releases #33 (Mistral Large 4 at $1.36/$4.18), merged after the last release.
@VickyXAI

Copy link
Copy Markdown
Contributor Author

Superseded by #34, which already pins router-core 8773a99 (a descendant of 3aca0e1, so the Gemini 4 Argon capability entry is shipped). Merging this would roll the pin back and undo router-core #10.

@VickyXAI VickyXAI closed this Oct 20, 2026
@VickyXAI
VickyXAI deleted the chore/router-core-3aca0e1 branch October 20, 2026 19:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant