Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion pyproject.toml
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ requires = ["setuptools>=77.0"]

[project]
name = "tesla_fleet_api"
version = "1.8.2"
version = "1.9.0"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge 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 👍 / 👎.

license = "Apache-2.0"
description = "Tesla Fleet API library for Python"
readme = "README.md"
Expand Down
2 changes: 1 addition & 1 deletion tesla_fleet_api/__init__.py
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
"""Tesla Fleet API"""

__author__ = "hello@teslemetry.com"
__version__ = "1.8.2"
__version__ = "1.9.0"

from tesla_fleet_api.const import Region, is_valid_region
from tesla_fleet_api.tariff import (
Expand Down
Loading