Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Source builds show update prompts because version 0.0.0 is treated as upgradeable [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#17167•Fetched 2026-04-09 08:01:40
View on GitHub
Comments
2
Participants
2
Timeline
9
Reactions
0
Author
vegerotvegerot
Participants
github-actions[bot]github-actions[bot]vegerotvegerot
Timeline (top)
labeled ×3commented ×2referenced ×2closed ×1

When Codex is run from a source build, the binary version can be 0.0.0. The update-check path treats that as a normal released version, so startup and popup update prompts may appear even though there is no upgrade path from a source build.

Root Cause

Suspected root cause

RAW_BUFFERClick to expand / collapse

Summary

When Codex is run from a source build, the binary version can be 0.0.0. The update-check path treats that as a normal released version, so startup and popup update prompts may appear even though there is no upgrade path from a source build.

Expected behavior

If the running version is a source-build sentinel like 0.0.0, Codex should skip the update prompt logic entirely.

Actual behavior

Codex still evaluates update availability and may show an upgrade prompt.

Reproduction

  1. Build or run Codex from source so the runtime version resolves to 0.0.0.
  2. Leave update checks enabled.
  3. Start the TUI or trigger the popup update path.
  4. Observe that Codex can report a newer version and prompt for upgrade.

Suspected root cause

The update-check entry points compare versions without first treating 0.0.0 as a non-released source build. The guard likely belongs in the shared update-path helpers so both startup checks and popup checks short-circuit consistently.

Affected area

codex-rs/tui/src/updates.rs

extent analysis

TL;DR

Modify the update-check logic to skip version comparisons when the running version is .0, indicating a source build.

Guidance

  • Identify the update-check entry points in codex-rs/tui/src/updates.rs and add a guard to treat 0.0.0 as a special case.
  • Modify the shared update-path helpers to short-circuit the update prompt logic when the version is 0.0.0.
  • Verify that the update prompt is skipped by running Codex from a source build with update checks enabled.
  • Review the version comparison logic to ensure it correctly handles the 0. case.

Example

if version == ".0" {
    // Skip update prompt logic for source builds
    return;
}

Notes

This fix assumes that the 0.0.0 version is only used for source builds and that the update-check logic is the primary cause of the issue.

Recommendation

Apply workaround: Modify the update-check logic to handle the 0. version as a special case, as this is a targeted fix for the identified issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

If the running version is a source-build sentinel like 0.0.0, Codex should skip the update prompt logic entirely.

#vector store#embedding generation#cache error#pipeline error#runtime error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING