Skip to content

fix(sync): sync upstream defaults to v3.12.3#45

Merged
srod merged 13 commits into
mainfrom
develop
Mar 24, 2026
Merged

fix(sync): sync upstream defaults to v3.12.3#45
srod merged 13 commits into
mainfrom
develop

Conversation

@srod
Copy link
Copy Markdown
Owner

@srod srod commented Mar 24, 2026

Sync the default model assignments to upstream oh-my-opencode v3.12.3.

Includes the librarian, ultrabrain, and unspecified-high updates, plus the matching test assertions and changeset.


Summary by cubic

Sync default model assignments to match upstream oh-my-opencode v3.12.3 and update tests to assert the new defaults. Also refresh CI/tooling (actions v6, Node 24, Bun 1.3.10) and enable Renovate.

  • Bug Fixes

    • agents.librarian -> opencode-go/minimax-m2.5
    • categories.ultrabrain -> openai/gpt-5.4 (xhigh)
    • categories.unspecified-high -> anthropic/claude-opus-4-6 (max)
  • Dependencies

    • CI: actions/checkout@v6, actions/setup-node@v6 (Node 24), Bun 1.3.10
    • Tooling: @changesets/changelog-github@^0.6.0; add renovate.json with config:recommended

Written for commit d7910e4. Summary will update on new commits.

renovate Bot and others added 13 commits March 9, 2026 18:19
chore(deps): update dependency bun to v1.3.10
…-0.x

chore(deps): update dependency @changesets/changelog-github to ^0.6.0
chore(deps): update actions/checkout action to v6
chore(deps): update actions/setup-node action to v6
chore(deps): update dependency node to v24
Update the synced defaults metadata and assignments to match oh-my-opencode v3.12.3.\n\nThis refreshes librarian, ultrabrain, and unspecified-high, updates the upstream sync assertions, and adds a patch changeset for the release.
@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Mar 24, 2026

🦋 Changeset detected

Latest commit: d7910e4

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
oh-my-opencode-config Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Mar 24, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 3751716b-3fb4-49dc-9ad5-31b99998da1f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch develop

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@qodo-code-review
Copy link
Copy Markdown

Review Summary by Qodo

Sync upstream defaults to oh-my-opencode v3.12.3

🐞 Bug fix ✨ Enhancement

Grey Divider

Walkthroughs

Description
• Sync default model assignments to oh-my-opencode v3.12.3
  - Update librarian from google/gemini-3-flash to opencode-go/minimax-m2.5
  - Update ultrabrain from openai/gpt-5.3-codex to openai/gpt-5.4
  - Update unspecified-high from openai/gpt-5.4 (high) to anthropic/claude-opus-4-6 (max)
• Update test assertions to match v3.12.3 upstream defaults
• Update CI/CD workflows to use actions/checkout@v6 and actions/setup-node@v6
• Update Node.js runtime to v24 and bun to v1.3.10
• Add renovate.json configuration for automated dependency management
Diagram
flowchart LR
  upstream["oh-my-opencode v3.12.3"]
  defaults["defaults.ts"]
  tests["defaults.test.ts"]
  deps["Dependencies & Actions"]
  
  upstream -- "sync model assignments" --> defaults
  defaults -- "update assertions" --> tests
  deps -- "update versions" --> ci["CI/CD Workflows"]
Loading

Grey Divider

File Changes

1. src/config/defaults.ts ✨ Enhancement +5/-5

Sync default model assignments to v3.12.3

• Updated librarian model from google/gemini-3-flash to opencode-go/minimax-m2.5
• Updated ultrabrain model from openai/gpt-5.3-codex to openai/gpt-5.4
• Updated unspecified-high model from openai/gpt-5.4 (high) to anthropic/claude-opus-4-6 (max)
• Updated source of truth reference from v3.11.1 to v3.12.3

src/config/defaults.ts


2. src/config/defaults.test.ts 🧪 Tests +6/-6

Update test assertions for v3.12.3 defaults

• Updated test description from v3.11.1 to v3.12.3
• Updated librarian assertion to expect opencode-go/minimax-m2.5
• Updated ultrabrain assertion to expect openai/gpt-5.4
• Updated unspecified-high assertion to expect anthropic/claude-opus-4-6 with max variant

src/config/defaults.test.ts


3. .changeset/neat-bugs-thank.md 📝 Documentation +5/-0

Add changeset for v3.12.3 sync

• Add patch changeset documenting sync of upstream defaults to v3.12.3
• Document updates to librarian, ultrabrain, and unspecified-high models

.changeset/neat-bugs-thank.md


View more (5)
4. .github/workflows/ci.yml ⚙️ Configuration changes +1/-1

Update checkout action to v6

• Update actions/checkout from v4 to v6

.github/workflows/ci.yml


5. .github/workflows/release.yml ⚙️ Configuration changes +4/-4

Update workflow actions and Node.js version

• Update actions/checkout from v4 to v6
• Update actions/setup-node from v4 to v6
• Update Node.js version from 22 to 24

.github/workflows/release.yml


6. package.json Dependencies +1/-1

Update changelog-github dependency

• Update @changesets/changelog-github from ^0.5.2 to ^0.6.0

package.json


7. .bun-version Dependencies +1/-1

Update bun runtime version

• Update bun version from 1.3.8 to 1.3.10

.bun-version


8. renovate.json ⚙️ Configuration changes +6/-0

Add renovate configuration

• Add new renovate configuration file
• Enable recommended renovate preset for automated dependency updates

renovate.json


Grey Divider

Qodo Logo

@qodo-code-review
Copy link
Copy Markdown

qodo-code-review Bot commented Mar 24, 2026

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (1) 📎 Requirement gaps (0) 📐 Spec deviations (0)

Grey Divider


Action required

1. Workflow adds Node.js setup 📘 Rule violation ⚙ Maintainability
Description
The release workflow configures Node.js via actions/setup-node, which introduces/maintains a
Node-specific workflow in a Bun-only repository. This violates the Bun-only tooling requirement and
can lead to inconsistent build/release behavior.
Code

.github/workflows/release.yml[R59-63]

      - name: Setup Node.js
-        uses: actions/setup-node@v4
+        uses: actions/setup-node@v6
        with:
-          node-version: "22"
+          node-version: "24"
          registry-url: "https://registry.npmjs.org"
Evidence
PR Compliance ID 1 prohibits introducing npm/yarn/pnpm/node-specific workflows. The changed lines in
release.yml explicitly set up Node.js (and update its version), which is a Node workflow
dependency.

AGENTS.md
.github/workflows/release.yml[59-63]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The release workflow sets up Node.js using `actions/setup-node`, which violates the repo requirement to avoid node/npm workflows and keep tooling Bun-only.

## Issue Context
This PR updated `actions/setup-node` and the configured Node version, meaning the PR is actively modifying a Node-based workflow dependency.

## Fix Focus Areas
- .github/workflows/release.yml[59-63]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools



Remediation recommended

2. Default model triggers doctor error 🐞 Bug ⛯ Reliability
Description
The new default librarian model can cause doctor to emit an ERROR (`model ... not found in
cache) whenever the local models cache doesn't contain opencode-go/minimax-m2.5`, even when the
user is using the default config (no config file yet, or after reset).
Code

src/config/defaults.ts[16]

+    librarian: { model: "opencode-go/minimax-m2.5" },
Evidence
When no config file exists, the CLI uses DEFAULT_CONFIG (which now includes
opencode-go/minimax-m2.5 for librarian). doctor validates each agent model by looking it up in
the merged models cache; if it's missing, it adds an error: `Agent "<name>" model
"<provider>/<model>" not found in cache. Therefore, if opencode-go/minimax-m2.5` is not present in
the cache, doctor will report an error for librarian on the default config.

src/config/loader.ts[6-12]
src/config/defaults.ts[11-23]
src/cli/commands/doctor.ts[316-354]
src/cli/commands/reset.ts[34-41]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`DEFAULT_CONFIG` now sets `agents.librarian.model` to `opencode-go/minimax-m2.5`. In `doctor`, any agent model missing from the local merged models cache is treated as an **error** (`model ... not found in cache`). This makes `doctor` report an error on the default config when the user’s environment/cache doesn’t include that provider/model.

### Issue Context
- Default config is returned when the config file is missing.
- `reset` writes `DEFAULT_CONFIG` to disk.
- `doctor` looks up each configured agent model in the cache and errors when not found.

### Fix Focus Areas
- src/config/defaults.ts[11-23]
- src/config/loader.ts[6-12]
- src/cli/commands/doctor.ts[316-354]
- src/cli/commands/reset.ts[34-41]

### What to change
Choose one concrete behavior change:
1) Prefer defaults that are expected to exist in typical caches/environments (change librarian default back to a more common provider/model), OR
2) Adjust `doctor` so that when the config is default-derived (or when cache is missing/outdated), missing-model lookups are downgraded from `error` to `warning` with an actionable suggestion (e.g., refresh cache / install provider), OR
3) On `reset` / first-run, proactively refresh/populate cache before writing defaults (only if consistent with CLI UX).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Grey Divider

ⓘ The new review experience is currently in Beta. Learn more

Grey Divider

Qodo Logo

Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 9 files

@srod srod merged commit ffffb94 into main Mar 24, 2026
4 checks passed
@github-actions github-actions Bot mentioned this pull request Mar 24, 2026
Comment on lines 59 to 63
- name: Setup Node.js
uses: actions/setup-node@v4
uses: actions/setup-node@v6
with:
node-version: "22"
node-version: "24"
registry-url: "https://registry.npmjs.org"
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Action required

1. Workflow adds node.js setup 📘 Rule violation ⚙ Maintainability

The release workflow configures Node.js via actions/setup-node, which introduces/maintains a
Node-specific workflow in a Bun-only repository. This violates the Bun-only tooling requirement and
can lead to inconsistent build/release behavior.
Agent Prompt
## Issue description
The release workflow sets up Node.js using `actions/setup-node`, which violates the repo requirement to avoid node/npm workflows and keep tooling Bun-only.

## Issue Context
This PR updated `actions/setup-node` and the configured Node version, meaning the PR is actively modifying a Node-based workflow dependency.

## Fix Focus Areas
- .github/workflows/release.yml[59-63]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant