oh-my-codex v0.21.18
0.21.18 is a patch release for the frozen range v0.21.17..8edbeb8686a9f7288b45f03d8f553a72216832f1 (2 commits, 4 files, +358/−27; PR #3819).
Highlights
- Preserve foreign hook trust (#3819, fixing #3818): clamp managed marker ranges at their first matching end, deduplicate repeated fences during refresh, and limit coordinate-family trust matching to indices OMX manages. Codex-approved foreign hook trust is preserved while tampered managed hashes remain fail-closed.
Compatibility
- Setup and doctor no longer treat approved foreign hook trust as a tampered managed-trust key when repeated OMX banners occur near the end of
config.toml. - Repeated managed fences are normalized during refresh; managed hook trust remains bounded to OMX-owned coordinates.
Validation
- Pinned candidate
8edbeb8686a9f7288b45f03d8f553a72216832f1: 17 latest-per-name check runs succeeded and 8 were skipped; none failed or remained incomplete. - Local checks passed:
npm run build:full,npm run build:runtime,npm run check:no-unused,npm run lint,npm run sync:plugin:check, andcargo metadata --locked --format-version 1 --no-deps. - Focused generator, setup-refresh, doctor-invalid-config, and plugin-cache regression tests: 105 passed.
Merged PR inventory
| PR | Author | Title |
|---|---|---|
| #3819 | @Yeachan-Heo | fix(config): clamp managed marker ranges and preserve foreign hook trust |
Issue #3818 was reported by @hetingyi.
Contributors
Thanks to @clawdbot and @Yeachan-Heo for contributing to this release.
Full Changelog: v0.21.17...v0.21.18
—
[repo owner's gaebal-gajae (clawdbot) 🦞]