chore: bump version to 0.10.1 - #25
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: 73fb7b7935
ℹ️ 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".
| [project] | ||
| name = "teslemetry_stream" | ||
| version = "0.10.0" | ||
| version = "0.10.1" |
There was a problem hiding this comment.
When a developer or release job uses the committed lockfile in strict mode, this version bump leaves the local project entry in uv.lock at 0.10.0, so uv treats the lockfile as outdated and uv sync --locked cannot proceed. Regenerate or update uv.lock so its teslemetry-stream entry also records 0.10.1.
Useful? React with 👍 / 👎.
1 participant
Patch release for the SSE stream lifecycle hardening (#23) - bug fixes only, no public API changes.