chore: bump gitlab-ai-provider to 6.16.0 - #50318
Merged
Merged
Conversation
github-actions
Bot
added
needs:compliance
Contributor
|
Thanks for your contribution! This PR doesn't have a linked issue. All PRs must reference an existing issue. Please:
See CONTRIBUTING.md for details. |
Contributor
|
The following comment was made by an LLM, it may be inaccurate: |
github-actions
Bot
removed
the
needs:compliance
Contributor
|
Thanks for updating your PR! It now meets our contributing guidelines. 👍 |
`opencode-gitlab-auth@3.0.0` is the first release built against the V2 plugin SDK (`@opencode/plugin`). Earlier 2.x releases target `@opencode-ai/plugin` and do not run under V2, so this repo had no working way to exercise the GitLab OAuth flow. The plugin adds a PKCE OAuth method and a self-managed instance URL field to the built-in `gitlab` integration. Everything else it used to do -- credential storage, refresh scheduling, and merging `instanceUrl`/`apiKey` into provider settings -- is now owned by core, so the plugin is only needed for the OAuth login path. `GITLAB_TOKEN` continues to work without it via the integration's `env` method. Pinned to an exact version so the config is reproducible.
vglafirov
changed the title
6 tasks
Revert the opencode-gitlab-auth@3.0.0 plugin entry added to .opencode/opencode.jsonc, restoring it to match v2.
vglafirov
changed the title
vglafirov
changed the title
6 tasks
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
2 participants
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 #50319
Type of change
What does this PR do?
Bumps the pinned
gitlab-ai-providerdependency inpackages/corefrom6.12.1to6.16.0(the current latest on npm), and updatesbun.lockaccordingly. This is the only place the package is declared.v2was six releases behind — the 6.13.0 (#46913), 6.15.0 (#47791), and now 6.16.0 bumps landed ondevbut never reachedv2. The span picks up new model mappings (duo-chat-fable-5-1,duo-chat-gpt-6-astra,duo-chat-opus-5-5), configurable reasoning controls, the workflow lock reconnect fix, and project-scoped Agent Platform model discovery.No source changes were needed. I diffed the published type declarations between
6.12.1and6.16.0and the changes are purely additive:GitLabThinkingConfigtype andthinkingoption for the Anthropic Messages models, plus areasoningEffortoption for the OpenAI models.DiscoveryScope({ projectId }preferred, withrootNamespaceIdas a fallback for older GitLab instances).discover,getEffectiveModelRef, anddiscoverModelsstill accept a bare string, which is what our call sites pass, so the existing signatures keep working.closeAndWait) to avoid racing the Workhorse lock on reconnect.duo-chat-opus-5-5/duo-workflow-opus-5-5mappings for Claude Opus 5.5 — no API surface changes.Every export we consume from
packages/core/src/plugin/provider/gitlab.ts(VERSIONand the dynamiccreateGitLabsurface) is unchanged, so this is a drop-in upgrade.This PR previously also loaded
opencode-gitlab-auth@3.0.0in.opencode/opencode.jsoncto exercise the GitLab OAuth login flow under the V2 plugin SDK. That config change has been dropped from this PR (see #50422, which reintroduces it alongside GitLab workflow discovery) so this PR stays a pure dependency bump.How did you verify your code works?
bun installfrom the repo root — lockfile resolves to6.16.0.bun typecheckinpackages/core— passes with no errors.bun test test/plugin/provider-gitlab.test.tsinpackages/core— 8 pass, 0 fail.bun run dev— the TUI boots and the GitLab Duo provider resolves as expected, including the newduo-chat-opus-5-5model.dist/index.d.tsbetween the two versions to confirm there are no breaking changes to the API surface we use.Screenshots / recordings
Not a UI change.
Checklist