chore(main): release 0.5.1 - #48
Conversation
![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: 173b054524
ℹ️ 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".
|
|
||
| [workspace.package] | ||
| version = "0.5.0" | ||
| version = "0.5.1" |
There was a problem hiding this comment.
This release bumps the workspace packages to 0.5.1, but Cargo.lock still records togl, togl-ffi, and togl-lib as 0.5.0 (Cargo.lock:924-953). I checked cargo check --help: --locked asserts that Cargo.lock remains unchanged, and the inspected CI/release workflows run Cargo with --locked (for example .github/workflows/ci.yml:49, .github/workflows/ci.yml:70, and .github/workflows/release.yml:200), so those jobs can fail as soon as Cargo tries to reconcile the lockfile with this bumped workspace version. Please include the cargo update --workspace/Cargo.lock changes in the release commit.
Useful? React with 👍 / 👎.
|
🤖 Created releases: 🌻 |
smorin-release-please
Bot
added
autorelease: tagged
and removed
autorelease: pending
labels
1 participant
🤖 I have created a release beep boop
0.5.1 (2026-07-16)
Bug Fixes
This PR was generated with Release Please. See documentation.