Repository navigation
chore(core): bump gitlab-ai-provider to 6.23.1 - #58999
Conversation
![opencode-agent[bot]](https://avatars.githubusercontent.com/in/1549082?s=60&v=4){kind=small}
There was a problem hiding this comment.
The bump looks good. Installing from this branch resolves gitlab-ai-provider 6.23.0, whose bundle includes the new duo-chat-haiku-5-5, duo-workflow-haiku-5-5 and duo-workflow-gemini-4-argon mappings. The GitLab provider tests pass (34/34), and packages/core type-checks cleanly with its typecheck:tsc command (tsc -b), because the bun check in the typecheck script isn't available in my Bun 1.4.2. The new transitive dependency proper-lockfile was already in bun.lock. The GitLab plugin only uses discoverWorkflowModels, VERSION and the provider factory, and nothing in core depends on the old strict tool default or the old refusal stop-reason handling. I couldn't run the new models end to end without GitLab credentials.
The public API is unchanged.
No concerns.
Related: #50843
|
Follow-up: anomalyco/models.dev#11474 publishes |
5a2899d to
98b0827
Compare
vglafirov
changed the title
There was a problem hiding this comment.
The new commit is a patch bump from 6.23.0 to 6.23.1, and 6.23.1 has the same dependency list as 6.23.0. I checked it again: install resolves 6.23.1 and its bundle still has the Haiku 5.5 mapping, the GitLab provider tests pass (34/34), and packages/core type-checks cleanly with its typecheck:tsc command (tsc -b). I couldn't run the new models end to end without GitLab credentials.
The public API is unchanged.
No concerns.
Issue for this PR
Closes #53831
Type of change
What does this PR do?
Bumps the pinned
gitlab-ai-providerinpackages/corefrom6.19.0to6.23.1. Thev1counterpart is #58998.bun.lockchanges only in that pin and the resolved package entry.6.23.1 (latest) adds the
duo-chat-haiku-5-5andduo-workflow-haiku-5-5(Claude Haiku 5.5) mappings and aduo-workflow-gemini-4-argonmapping. The models.dev entry forduo-chat-haiku-5-5is stillv2_onlyand will be published toapi.jsononce both opencode lines ship this bump. Otherwise the model would appear in the picker and then fail withUnknown model ID.Other provider changes since 6.19.0: Duo Agent Platform now works on self-managed instances (WebSocket namespace fallback, provider-level
workflowOptionsdefaults), Responses API tools now default tostrict: false, an Anthropicrefusalstop reason maps tocontent-filter, and there are two new opt-in options (skipCache, shared direct-access token cache). The GitLab plugin doesn't hardcode model ids and the provider API it uses didn't change, so no source changes were needed.How did you verify your code works?
bun install(Bun 1.4.4):packages/coreresolvesgitlab-ai-provider6.23.1from npm, and the installeddist/contains the Haiku 5.5 ids.bun run typecheckinpackages/corepasses.bun test test/plugin/provider-gitlab.test.ts test/plugin/provider-gitlab-oauth.test.tsgives 34 pass, 0 fail.packages/core:bun run testgives 6801 pass, 0 fail.Screenshots / recordings
Not a UI change.
Checklist
Added by the opencode bot (AI-generated).
Related: #50843