Conversation
…43-01a07240 [WRONG BRANCH] chore(release): promote verified candidate to 2.43.0
…lease-244-main-07c0
…in-07c0 chore(release): promote validated 2.44.0 to main
Promote frozen dev source cf9f662; no new runtime changes. Candidate CI34061274315 and service34061276621 are the validation references. Publication waits for successful validation and the final main push CI at the exact release SHA.
Promote frozen dev source cf9f662 as 2.45.0. The repository owner explicitly authorized this main/preview release promotion and admin PR-only merge. This is a release-specific owner decision, not an independent approval or the dev-only maintainer exception. Frozen candidate full CI34061274315 passed all25jobs after one unchanged-source rerun of Windows5; the initial holder busy assertion remains recorded without a root-cause resolution claim. Service lifecycle34061276621 passed Linux/macOS/Windows. Dev version pre-move3812 is merged. Publication still requires this actual main merge SHA's own successful push CI and Service lifecycle. No local suites were run.
[WRONG BRANCH] chore(release): promote verified 2.46.0 to main
[WRONG BRANCH] release: promote 2.47.0 to main
[WRONG BRANCH] release: apply final roster correction to main
[WRONG BRANCH] release: promote 2.48.0 to main
…in-01a08498 release: promote verified 2.49.0 product tree to main
…in-01a08a81 [WRONG BRANCH] release: promote verified 2.50.0 product tree to main
[WRONG BRANCH] release: promote verified 2.51.0 product tree to main
Product tree is dev at 7bfb2ad. Only package.json differs, carrying the stable channel version 2.52.0. This promotion follows a CI repair and a regression sweep: dev had drifted 79 commits past its last finished run and the one run allowed to complete had failed. lidge-jun#4390 fixed an integration test that never denied anything and had been red on dev since lidge-jun#4342; lidge-jun#4396/lidge-jun#4397/lidge-jun#4398 closed four gaps in the quota avoidance contract lidge-jun#4368 introduced; lidge-jun#4403 made a port fixture deterministic.
release: promote verified 2.52.0 product tree to main
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: 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. Comment |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 628209080a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "deepseek/deepseek-v4-pro", | ||
| "opencode-go/deepseek-v4-pro", |
There was a problem hiding this comment.
This changes the src/codex/ catalog contract but updates only structure/catalog.md; the ownership table also lists runtime.md, config.md, codex-home.md, subagents.md, providers/openai-tiers.md, gui-and-management-api.md, and ops/docs-and-release.md. Review and update each listed document in this change so their descriptions remain synchronized with the new compatibility exclusions.
AGENTS.md reference: src/AGENTS.md:L11-L11
Useful? React with 👍 / 👎.
|
✅ Deterministic PR hygiene checks passed. |
github-actions
Bot
changed the title
⏳ DRAFT
What to do
Its title has been prefixed with |
2 participants
Motivation
deepseek-v4-prorows fordeepseekandopencode-go, exposing stale aliases in the routed catalog.augmentRoutedModelsWithMetadataadds metadata rows before the compatibility filter.Description
"deepseek/deepseek-v4-pro"and"opencode-go/deepseek-v4-pro"toROUTED_MODEL_COMPATIBILITY_EXCLUSIONSinsrc/codex/catalog/parsing.tsso metadata-augmented rows are dropped byshouldExposeRoutedModel.tests/codex-integration/codex-catalog.test.tsthat verifyshouldExposeRoutedModelreturnsfalsefor bothdeepseek/deepseek-v4-proandopencode-go/deepseek-v4-prowhile keeping positive controls for live models.structure/catalog.mdto note that generated historical metadata may retain retired aliases and that compatibility exclusions are applied after live discovery and augmentation.Testing
npx --yes bun@1.4.2 test tests/codex-integration/codex-catalog.test.ts --test-name-pattern 'still filters compatibility-excluded slugs' --dots, and the focused test passed.npx --yes bun@1.4.2 run structure:check,npx --yes bun@1.4.2 run typecheck, andnpx --yes bun@1.4.2 run privacy:scan, all of which succeeded.npx --yes bun@1.4.2 run test; the focused change is covered, but the full suite failed in this environment due to unrelated, container-sensitive timeouts and process-group test expectations, and not because of this change.Codex Task