From bfe90188add9603c0908501e93b2b112f623f373 Mon Sep 17 00:00:00 2001 From: "Adam Perry @ OpenAI" Date: Tue, 16 Jun 2026 17:18:20 -0700 Subject: [PATCH] Revert "Tell codex about PathUri serde compat. (#28595)" (#28627) This reverts commit bd2a78632665006149d6e7df627c52ebc1b3464e, which didn't capture all the nuance we need for this migration. --- .codex/skills/path-types/SKILL.md | 7 ------- 1 file changed, 7 deletions(-) diff --git a/.codex/skills/path-types/SKILL.md b/.codex/skills/path-types/SKILL.md index de35714dd..ccf1a9f41 100644 --- a/.codex/skills/path-types/SKILL.md +++ b/.codex/skills/path-types/SKILL.md @@ -19,13 +19,6 @@ migration; if compliance is difficult, ask the user how to proceed. - Tool call arguments that the model is expected to generate should be deserialized as regular `String`s with feature-specific path handling code. -## Rollout stability - -Assume that rollouts will be parsed by monotonically increasing versions of Codex. - -You can use `PathUri` in place of `AbsolutePathBuf` for rollout fields without jeopardizing -backwards compatibility since `PathUri` allows deserialization from bare absolute paths. - ## Migration requirements Keep these requirements in mind while migrating code to conform with the above guidelines: