Skip to content

Fix codex-termux manifest synchronization - #127

Merged
bash0816 merged 1 commit into
mainfrom
fix/codex-manifest-sync
Jul 17, 2026
Merged

Fix codex-termux manifest synchronization#127
bash0816 merged 1 commit into
mainfrom
fix/codex-manifest-sync

Conversation

@bash0816

Copy link
Copy Markdown
Owner

Fix codex-termux manifest synchronization between root and package configs

Summary

  • Update 0.144.5 manifest data: previous_stable_version to 0.144.4 (matches current npm latest)
  • Update package manifest: latest_candidate_version to 0.144.5
  • Refactor update-codex-candidate-manifest.js to support dual-file sync with single timestamp generation
  • Add test coverage for manifest synchronization (7 test cases)
  • Update workflows to include both manifests and add verification guard

Changes

  1. Manifest Data: Root and package configs now have correct version references for 0.144.5 intake
  2. Script Refactor: update-codex-candidate-manifest.js now exports testable updateManifests() function and updates both files atomically
  3. Test Suite: 7 tests verify version updates, timestamp identity, and field preservation
  4. Workflow Updates:
    • codex-version-watch.yml: both manifests now committed
    • promote-and-publish.yml: new guard step validates previous_stable_version matches npm registry before latest promotion
  5. YAML Validation: both workflows pass syntax check

…nfigs

- Update 0.144.5 manifest data: previous_stable_version to 0.144.4 (matches current npm latest)
- Update package manifest: latest_candidate_version to 0.144.5
- Refactor update-codex-candidate-manifest.js to export updateManifests function for testability
- Ensure updated_at timestamp is identical in both root and package manifests (single Date generation)
- Add comprehensive tests for manifest synchronization (7 test cases)
- Update codex-version-watch.yml to include package manifest in git add
- Add verification guard in promote-and-publish.yml to validate previous_stable_version matches npm registry latest before promotion
@bash0816
bash0816 merged commit 8fbd508 into main Jul 17, 2026
4 of 5 checks passed
@bash0816
bash0816 deleted the fix/codex-manifest-sync branch July 17, 2026 00:57

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e8f6ef5285

ℹ️ 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".

Comment on lines +29 to +31
rootManifest.latest_candidate_version = candidateVersion;
rootManifest.candidate_state_status = candidateState;
rootManifest.updated_at = updatedAt;

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Set previous_stable_version during new intake

When the next candidate is ingested after this release finalizes, scripts/finalize-update-docs.sh only advances latest_audited_version and leaves previous_stable_version at the prior value; this function then starts the new candidate without deriving previous_stable_version from the current audited/latest version. The new guard in .github/workflows/promote-and-publish.yml compares that stale field to npm latest, so promoting the following release (for example 0.144.6 after 0.144.5 is latest) will fail until the manifest is manually edited. Please update previous_stable_version for both manifests when starting a new candidate, or move that maintenance into finalization.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant