chore(main): release ejector 0.7.1#21739
Conversation
taiko-kitty
requested review from
RogerLamTd,
YoGhurt111 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: 444a352ce8
ℹ️ 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.7.0" | ||
| version = "0.7.1" |
There was a problem hiding this comment.
This release bumps the crate to 0.7.1, but the tracked packages/ejector/Cargo.lock still records the local ejector package as 0.7.0 (checked at packages/ejector/Cargo.lock:1848-1849). The release config explicitly lists that lockfile package version as an extra-files target for packages/ejector, so the release commit leaves the repository's published release metadata inconsistent and the next release-please run will have to repair this instead of starting from the released state.
Useful? React with 👍 / 👎.
taiko-kitty
force-pushed
the
release-please--branches--main--components--ejector
branch
3 times, most recently
from
caf053c to
727e718
Compare
taiko-kitty
force-pushed
the
release-please--branches--main--components--ejector
branch
3 times, most recently
from
9716da7 to
0f2c9f1
Compare
taiko-kitty
force-pushed
the
release-please--branches--main--components--ejector
branch
from
0f2c9f1 to
9ef9438
Compare
1 participant
🤖 I have created a release beep boop
0.7.1 (2026-06-15)
Chores
v1.1.1(#21737) (729a43e)This PR was generated with Release Please. See documentation.