Repository navigation
chore: bump gitlab-ai-provider to 6.23.1 - #58998
Merged
rekram1-node merged 1 commit intoOct 26, 2026
Merged
Conversation
This was referenced Oct 25, 2026
Contributor
Author
|
Follow-up: anomalyco/models.dev#11474 publishes |
vglafirov
force-pushed
the
bump-gitlab-ai-provider-6-23-0-v1
branch
from
October 25, 2026 15:28
fdb5037 to
b6b7794
Compare
vglafirov
changed the title
kartamyshev-dev
pushed a commit
to gooddaytoday/loginom-ai-agent
that referenced
this pull request
Oct 28, 2026
…5 merge The packages/opencode/package.json resolution reused the LAB-378 file and dropped the non-conflicting upstream bump 6.19.0 -> 6.23.1 (anomalyco#58998), found by LAB-392 (F1). bun.lock regenerated with Bun 1.3.14; the decision record for the path notes the correction. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Issue for this PR
Closes #53831
Type of change
What does this PR do?
Bumps the pinned
gitlab-ai-providerfrom6.19.0to6.23.1inpackages/coreandpackages/opencodeonv1. Thev2counterpart (dev,packages/coreonly) is #58999.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 provider API opencode uses didn't change, so no source changes were needed.bun.lockchanges only in the two pins and the resolved package entry, plus asignal-exitre-hoist: 6.23.x addsproper-lockfile, which needssignal-exit@3.How did you verify your code works?
bun install(Bun 1.4.4): both packages resolvegitlab-ai-provider6.23.1from npm, and the installeddist/contains the Haiku 5.5 ids.bun run typecheckpasses inpackages/coreandpackages/opencode.packages/core:bun testgives 1102 pass, 0 fail.packages/opencode:bun test test/provider/gitlab-duo.test.ts test/provider/provider.test.ts test/provider/transform.test.tsgives 688 pass, 0 fail.Screenshots / recordings
Not a UI change.
Checklist