[FEATURE]: Bump gitlab-ai-provider to 6.18.0 on dev (adds GPT-6 Sol and Luna)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 90/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- gitlab, nodejs, typescript
Research direction
Update the gitlab-ai-provider version in package.json files in packages/opencode and packages/core from the specified versions to 6.18.0. Then run the package manager (likely bun) to update the lockfile. Verify the changes by checking the lockfile and ensuring the new model mappings are available.
Written by the indexing model from the issue text.
Description
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Bump the pinned gitlab-ai-provider dependency on dev to 6.18.0, the current latest on npm, in both places it's declared:
packages/opencode(the v1 app):6.15.0→6.18.0. This pin was missed by the previous bump (#50741), which only touchedpackages/core.packages/core:6.16.0→6.18.0.
What the new releases bring:
- 6.16.0: Claude Opus 5.5 mappings, and Agent Platform workflow discovery scoped by project with stale workflow refs corrected. This is the first time
packages/opencodepicks these up. - 6.17.0: optional per-account
cacheKeyfordiscoverWorkflowModels(). It's additive, so the v1 call site is unchanged and existing cache entries keep their keys. - 6.17.1: the exported
VERSION(sent in the GitLabUser-Agent) had always reported the previous release; it's now correct. The package also no longer ships a copy of its own tarball, which roughly halves its size. - 6.18.0:
duo-chat-gpt-6-solandduo-chat-gpt-6-lunamodel mappings.
No source changes are needed; this is a dependency bump plus bun.lock.
- Dominant language
- TypeScript
- Stars
- 210k
- Forks
- 27.8k
- Avg merge
- 5h 53m
- Merged PRs (30d)
- 358
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from anomalyco/opencode
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
anomalyco/opencode#51159 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
All issues in anomalyco/opencode
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
automated issue report
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 92/100
github/copilot-sdk#2804 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
drizzle-team/drizzle-orm#6418 ·
Maintainers usually reply within 4 days
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
diegosouzapw/OmniRoute#15307 · 1 comment ·
Maintainers usually reply within 2 days