Bump version to 1.9.0 - #121
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 40d4748ef3
ℹ️ 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 = "tesla_fleet_api" | ||
| version = "1.8.2" | ||
| version = "1.9.0" |
There was a problem hiding this comment.
Regenerate uv.lock for the bumped project version
When consumers run uv sync --locked or uv lock --check, this change makes the project metadata disagree with the tracked lockfile, whose editable tesla-fleet-api entry still declares version 1.8.2 at uv.lock:742-744. The local uv sync --help defines --locked as asserting that uv.lock remains unchanged; checking this checkout therefore attempts to resolve a new lock and fails in locked/offline environments, whereas restoring the metadata to 1.8.2 passes the same check. Include the generated uv.lock version update with this bump.
Useful? React with 👍 / 👎.
Bump version to 1.9.0 (minor) for PR #120, which added the Teslemetry OAuth dynamic client registration helper.
Full validation pipeline is skipped per the standing small-change rule for bump-only diffs; ruff, pyright, and pytest were run locally and pass.