chore(main): release 0.17.0 - #151
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: 611f4643d0
ℹ️ About Codex in GitHub
Your team has set up Codex to 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 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| [package] | ||
| name = "any-console-server" | ||
| version = "0.16.0" | ||
| version = "0.16.1" |
There was a problem hiding this comment.
When this release commit is checked out, server/Cargo.toml reports 0.16.1 while the any-console-server entry in server/Cargo.lock remains 0.16.0. The repository's .github/workflows/sync-release-lockfile.yml:3-7 explicitly identifies this mismatch as causing the first post-release Cargo build to modify the lockfile; include the generated lockfile update in the release commit so the tagged source builds without leaving an uncommitted change.
Useful? React with 👍 / 👎.
cfe03b9 to
ffdec09
Compare
90b54d0 to
13c97bb
Compare
dcc06c5 to
c8b4df2
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c8b4df27a1
ℹ️ About Codex in GitHub
Your team has set up Codex to 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 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| [package] | ||
| name = "any-console-server" | ||
| version = "0.16.0" | ||
| version = "0.17.0" |
There was a problem hiding this comment.
Fresh evidence in this revision is that the release version has advanced to 0.17.0, but the any-console-server entry in server/Cargo.lock is still 0.16.0. The repository's .github/workflows/sync-release-lockfile.yml documents that this mismatch makes the first post-release Cargo build rewrite the lockfile, and the preceding 0.16.0 release contains a dedicated lockfile-sync commit, so this release commit should include the equivalent generated update.
Useful? React with 👍 / 👎.
8fb9ff7 to
fff6df6
Compare
9528e20 to
af7c067
Compare
1 participant
🤖 I have created a release beep boop
0.17.0 (2026-09-05)
Features
Bug Fixes
Refactor
Documentation
Build
This PR was generated with Release Please. See documentation.