Repository navigation
Release Cove1.0.0 with verified source installation and handoffs - #6
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a99e231913
ℹ️ 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".
| if (context.eventName !== 'push' || context.ref !== 'refs/heads/main' || | ||
| !/^[0-9a-f]{40}$/.test(context.sha)) { | ||
| throw new Error('Publishing requires a main push with an exact commit SHA.'); |
There was a problem hiding this comment.
When another commit is pushed while an earlier run is still verifying, the earlier run retains its event context.sha; this guard only confirms that the event targeted main, while the publish job explicitly keeps in-progress releases running. If both commits still declare version 1.0.0, the older run can publish that version after main advances, and the newer run then returns because the release is already published, permanently excluding the newer commit. Query heads/main immediately before publication and require its SHA to equal context.sha.
Useful? React with 👍 / 👎.
1 participant
Define Cove 1.0.0 across the public website, installed Codex plugin, and source-installed PostgreSQL edition. Add a versioned source ZIP with checksums, setup and upgrade guidance, and a bounded compatibility contract while preserving dated verification records.
Update the MCP client to 2.2.0 and Sharp to 0.35.5 for their published patches, keeping the remaining framework/runtime versions unchanged. Package and publish only the exact main commit after the existing verification, recovery, and source-package jobs pass; PR checks remain read-only.
Fresh local validation passed 24 existing tests, both production builds, dependency audit, a normal signup/save/handoff/export/import/mobile journey, container restart and backup/restore, and installation/build from the extracted source ZIP. The actual installed connector passed exact readback, retries/conflicts, and fresh pinned-handoff continuation with newer context present. Independent review found no candidate blockers.
Final public CI, release assets and the corresponding Sites deployment will be verified before declaring v1 delivered. A separate ChatGPT web assistant host and production disaster recovery are outside the recorded verification.