Skip to content

Add sync-reminder workflow; bump to 0.2.3#3

Merged
avifenesh merged 3 commits into
mainfrom
add-sync-reminder
May 22, 2026
Merged

Add sync-reminder workflow; bump to 0.2.3#3
avifenesh merged 3 commits into
mainfrom
add-sync-reminder

Conversation

@avifenesh
Copy link
Copy Markdown
Collaborator

Added

  • A sync reminder CI workflow that opens (or updates) a codex-sync-labeled 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 — re-applying its codex naming (codex-* / CODEX_COMPUTER_USE_*, com.openai.Codex.* DBus, identity.rs, chrome-extension host). Merge, do not overwrite.

Changed

  • Bump to 0.2.3 to establish version-enumeration parity with the codex-desktop-linux embedded 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

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.
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

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.

Comment thread CHANGELOG.md Outdated
Comment on lines +13 to +16
- 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.
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

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.

avifenesh added 2 commits May 22, 2026 06:58
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.
@avifenesh
Copy link
Copy Markdown
Collaborator Author

Re @gemini-code-assist review:

  • Workflow file is present.github/workflows/sync-reminder.yml is included in this PR (gh pr diff --name-only lists it); it isn't missing. The Gemini diff view may have skipped the .github/ path.
  • Label name — good call; the changelog entry now names both the file and the codex-sync label (e09d7dc).

Also fixed the failing MCP safety contract gate: the tool_handler server version was still 0.2.2 while Cargo was bumped to 0.2.3 — now aligned.

@gemini-code-assist
Copy link
Copy Markdown

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.

@avifenesh avifenesh merged commit 7d2073f into main May 22, 2026
20 checks passed
@avifenesh avifenesh deleted the add-sync-reminder branch May 22, 2026 04:11
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