openai/codex
1
0
Fork 0
mirror of https://github.com/openai/codex.git synced 2026-10-30 19:18:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

Prefer documented replacements for deprecation-driven model migrations (#58134)

Browse Source 
## What changed

Update the `openai-docs` skill's model migration guidance to use the retiring model's documented replacement from the API deprecations page when no explicit target is given. Fall back to the latest-model resolver when no replacement is documented or the migration is not prompted by a deprecation.

GitOrigin-RevId: db51a2a034118f05fc6b9b30c763231205b784e5
This commit is contained in:
Konstantine Kahadze
2026-10-29 17:49:51 +00:00
committed by copyberry
parent 03b7e22f94
commit 7d764a236e
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
codex-rs/skills/src/assets/samples/openai-docs/references/model-migration.md
+1 -1
View File
@@ -5,7 +5,7 @@ Use this route for model upgrades, migration planning, model-specific prompting,
## Choose the target before loading more context
- **Explicit model target:** Preserve the user's exact requested target, including an explicitly requested GPT-5.5 or GPT-5.6 migration. Do not run the latest-model resolver and do not substitute a newer model. Search for and fetch current guidance for that exact model. A GPT-5.6 migration must not load GPT-6 guidance or references.
- **Unspecified, latest, current, or default target:** Search for and fetch `https://developers.openai.com/api/docs/guides/latest-model` first. Use the corresponding `latest-model.md` metadata only when dynamic migration resolution is needed, then run the platform-specific resolver below and preserve its returned model and exact guide URLs.
- **Unspecified, latest, current, or default target:** For deprecation-driven migrations, use the retiring model's documented replacement from the [API deprecations page](https://developers.openai.com/api/docs/deprecations) instead of running the latest-model resolver. If no replacement is documented, or the migration is not prompted by a deprecation, search for and fetch `https://developers.openai.com/api/docs/guides/latest-model` first. Use the corresponding `latest-model.md` metadata only when dynamic migration resolution is needed, then run the platform-specific resolver below and preserve its returned model and exact guide URLs.
- **Latest/current/default prompting:** Follow the dynamic-target route, then use the returned prompting guide. Do not run the resolver for explicitly named-model prompting.
- **Pure model selection:** Use `references/model-selection.md` instead. Do not run the resolver.