chore: bump version to 1.7.2#75
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Intent
Cut python-tesla-fleet-api release 1.7.2. This is a pure version-bump release train: both constituent PRs (#73 fix(fleet): handle non-object JSON command logging - fixes a prod Powerwall-500 regression where TeslemetryEnergySite calls that return null/list/scalar JSON bodies crashed _log_request_result's logging convenience code; and #74 fix(tesla): create private keys atomically with owner-only permissions via O_EXCL 0600) are already merged to main. The only change in this PR is bumping version from 1.7.1 to 1.7.2 in pyproject.toml and tesla_fleet_api/init.py, following the exact same mechanics as the 1.7.0 and 1.7.1 version-bump cuts (see PRs #69 and #71 in this repo's history). No functional code changes, no new features - just the release version bump commit. uv.lock is expected to also get its tesla-fleet-api version entry updated (either by me or by the no-mistakes document/lint step, matching how the 1.7.1 bump PR handled it).
What Changed
1.7.1to1.7.2inpyproject.tomlandtesla_fleet_api/__init__.py.uv.lockandtesla_fleet_api.egg-info/PKG-INFOso all packaged version references agree.Risk Assessment
✅ Low: The reviewed delta is limited to internally consistent 1.7.1 to 1.7.2 release metadata updates across pyproject, package version, uv.lock, and tracked egg-info, with no functional code changes.
Testing
Diff inspection confirmed the release bump surfaces moved to 1.7.2,
uv buildproduced wheel and sdist artifacts named and stamped 1.7.2, archive inspection confirmed wheel metadata, sdist metadata, and package__version__agree, anduv run pytest testspassed.Evidence: Release version evidence
Built artifacts: tesla_fleet_api-1.7.2-py3-none-any.whl tesla_fleet_api-1.7.2.tar.gz Wheel METADATA version: Metadata-Version: 2.4 Name: tesla_fleet_api Version: 1.7.2 Wheel package version line: version = "1.7.2" Sdist PKG-INFO version: Metadata-Version: 2.4 Name: tesla_fleet_api Version: 1.7.2/tmp/no-mistakes-evidence/01KXAZV7EAQAJ4C4RY9HTCFTY1/dist/tesla_fleet_api-1.7.2-py3-none-any.whl) - Evidence: Built sdist (local file:/tmp/no-mistakes-evidence/01KXAZV7EAQAJ4C4RY9HTCFTY1/dist/tesla_fleet_api-1.7.2.tar.gz)Pipeline
Updates from git push no-mistakes
✅ **intent** - passed
✅ No issues found.
✅ **Rebase** - passed
✅ No issues found.
🔧 **Review** - 1 issue found → auto-fixed (2) ✅
pyproject.toml:7- The release metadata now says 1.7.2, but the checked-inuv.lockstill records the editabletesla-fleet-apipackage as 1.7.1. Update/regenerate the lockfile so the release bump is internally consistent.🔧 Fix: Sync release lockfile version
1 warning still open:
tesla_fleet_api.egg-info/PKG-INFO:3- The tracked egg-info metadata still reports Version: 1.7.1 while the package/version constants were bumped to 1.7.2. Because this file is tracked and was consistent at the base commit, the release bump now leaves repository metadata internally inconsistent; regenerate or update the egg-info metadata for the release.🔧 Fix: Sync egg-info release version
✅ Re-checked - no issues remain.
✅ **Test** - passed
✅ No issues found.
git diff --unified=3 c618141495b61eab18f40033fd6fef66a82a0a9c..684e6c0c2c583bded3cc08dde107201139b08bcb -- pyproject.toml tesla_fleet_api/__init__.py uv.lock tesla_fleet_api.egg-info/PKG-INFOrg -n "1\.7\.[0-9]|version =|__version__|Version:" pyproject.toml tesla_fleet_api/__init__.py uv.lock tesla_fleet_api.egg-info/PKG-INFOuv build --out-dir /tmp/no-mistakes-evidence/01KXAZV7EAQAJ4C4RY9HTCFTY1/distuv run pytest testsunzip/tarinspection recorded in/tmp/no-mistakes-evidence/01KXAZV7EAQAJ4C4RY9HTCFTY1/release-version-evidence.txtCleanup/status check: removed transient.venv, restored build-regeneratedtesla_fleet_api.egg-info/PKG-INFO, and confirmed no worktree test artifacts remained✅ **Document** - passed
✅ No issues found.
✅ **Lint** - passed
✅ No issues found.
✅ **Push** - passed
✅ No issues found.