Add sync-reminder workflow; bump to 0.2.3#3
Conversation
Add a sync-reminder CI workflow that opens an issue when main touches the crate sources, so changes can be propagated into the codex-desktop-linux embedded copy (re-applying its codex naming). Bump to 0.2.3 to establish version-enumeration parity with the embedded copy (codex-desktop-linux carries 0.2.3-linux-alpha1). The two crates are kept on the same enumeration: a mismatch signals a pending sync between them.
There was a problem hiding this comment.
Code Review
This pull request bumps the version of the computer-use-linux crate to 0.2.3 and updates the CHANGELOG.md to include details about a new sync reminder CI workflow. Feedback indicates that the actual workflow configuration file mentioned in the changelog is missing from the changes and suggests including the specific label name in the documentation for clarity.
| - A `sync reminder` CI workflow that opens (or updates) an issue when a merge to | ||
| `main` touches the crate sources (`src/**`, `Cargo.toml`, | ||
| `gnome-shell-extension/**`), so the change can be propagated into the | ||
| `codex-desktop-linux` embedded copy with its codex naming re-applied. |
There was a problem hiding this comment.
The pull request title and this changelog entry indicate the addition of a sync reminder CI workflow. However, the actual workflow configuration file (e.g., .github/workflows/sync-reminder.yml) is missing from the changes in this pull request. Please ensure the workflow implementation is included.
Additionally, for better documentation, consider specifying the label name (codex-sync) mentioned in the PR description within this entry.
The npm wrapper CI gate asserts Cargo.toml version == package.json version.
…elog The MCP safety contract CI gate asserts the tool_handler server version equals the Cargo version; bump it to 0.2.3 to match. Also name the workflow file and the codex-sync label in the changelog entry.
|
Re @gemini-code-assist review:
Also fixed the failing |
|
Thanks for the clarification, avifenesh. It sounds like the workflow is correctly configured and the version alignment issue is resolved. The updates to the changelog and the version bumps across the codebase look correct and consistent with the project's versioning strategy. |
Added
sync reminderCI workflow that opens (or updates) acodex-sync-labeled issue when a merge tomaintouches the crate sources (src/**,Cargo.toml,gnome-shell-extension/**), so the change can be propagated into thecodex-desktop-linuxembedded copy — re-applying its codex naming (codex-*/CODEX_COMPUTER_USE_*,com.openai.Codex.*DBus,identity.rs, chrome-extension host). Merge, do not overwrite.Changed
0.2.3to establish version-enumeration parity with thecodex-desktop-linuxembedded copy (0.2.3-linux-alpha1). The two crates are kept on the same enumeration on purpose: a mismatch signals a pending sync between them.Counterpart PR (embedded copy receiving the 0.2.2 feature sync): ilysenko/codex-desktop-linux#274