Conversation
taiko-kitty
requested review from
MatusKysel and
davidtaikocha
as code owners
![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: bee8c81043
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| [package] | ||
| name = "ejector" | ||
| version = "0.5.0" | ||
| version = "0.6.0" |
There was a problem hiding this comment.
The package version was bumped to 0.6.0 in packages/ejector/Cargo.toml, but packages/ejector/Cargo.lock still records the root ejector package as 0.5.0 (line 1800), which leaves the lockfile out of sync with the manifest. Any workflow or local build that enforces locked resolution (for example cargo build --locked/cargo test --locked) will fail until the lockfile is regenerated, so the release commit should include the corresponding Cargo.lock update.
Useful? React with 👍 / 👎.
taiko-kitty
force-pushed
the
release-please--branches--main--components--ejector
branch
7 times, most recently
from
1da6b9a to
42a3b66
Compare
taiko-kitty
force-pushed
the
release-please--branches--main--components--ejector
branch
4 times, most recently
from
ca29c0c to
f5f7556
Compare
taiko-kitty
force-pushed
the
release-please--branches--main--components--ejector
branch
from
f5f7556 to
db60831
Compare
1 participant
🤖 I have created a release beep boop
0.6.0 (2026-02-21)
Features
This PR was generated with Release Please. See documentation.