Repository navigation
chore(deps): bump subswitch to 0.6.0 - #461
Merged
Merged
Conversation
Exact pin, lockfile touched only for the subswitch entry. The 0.5.0 and 0.6.0 packages were diffed: only the model registries, two init hint strings and the version constant differ. The config schema, the legacy key table, the env reads and the models --json shape are byte-identical, so no devflow code changes. 0.6.0 adds gpt-6.1-sol, claude-sonnet-5-5 and claude-haiku-5-5, and moves the sol, sonnet and haiku aliases to them. Devflow derives aliases from models --json at run time, so no hand-kept list needed an update. The version pin in the packaging test, the registry-id fixture comments and the contract comments in proxy-state and proxy-log now name 0.6.0. Every id in the exact-id fixture is still in the 0.6.0 registry.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Pins the routing runtime at
subswitch@0.6.0(was0.5.0) as an exact pin independencies. The lockfile changes only thesubswitchentry. This is a routine dependency bump requested directly by the maintainer.Changes
package.json:subswitchmoves from0.5.0to0.6.0, an exact pin independencies.package-lock.json: only thesubswitchentry changes (the root declaration, plus the version, resolved URL and integrity ofnode_modules/subswitch).gpt-6.1-sol,claude-sonnet-5-5andclaude-haiku-5-5. Thesol,sonnetandhaikualiases now resolve to them. Config handling and env-var reads are byte-identical to 0.5.0, and themodels --jsonfield shape is unchanged.src/core/proxy-log.ts,src/core/proxy-state.tsand three test files move to0.6.0. TheSUBSWITCH_VERSIONpin intests/packaging.test.tsdoes too.CHANGELOG.md:[Unreleased]entry for the bump.models --json.Breaking Changes
None. One behaviour change to know about: an agent routed through
sol,sonnetorhaikumoves to the newer model at its next session. To keep an agent on a fixed model, pin an exact ID withdevflow agents --set <agent> --model <id>.Testing
Related Issues
None. No tracker issue; routine dependency bump requested directly by the maintainer.