Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump Tesla Fleet API to v0.9.12 #139565

Merged
merged 5 commits into from
Mar 1, 2025
Merged

Conversation

Bre77
Copy link
Contributor

@Bre77 Bre77 commented Mar 1, 2025

Proposed change

Bump to Tesla Fleet API library to fix a command signing issue in tesla_fleet.

Teslemetry/python-tesla-fleet-api@v0.9.10...v0.9.12

Please milestone for 2025.3 and beta

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New integration (thank you!)
  • New feature (which adds functionality to an existing integration)
  • Deprecation (breaking change to happen in the future)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Additional information

Checklist

  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • I have followed the perfect PR recommendations
  • The code has been formatted using Ruff (ruff format homeassistant tests)
  • Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • The manifest file has all fields filled out correctly.
    Updated and included derived files by running: python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
  • For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

@Bre77 Bre77 marked this pull request as ready for review March 1, 2025 11:50
@Bre77 Bre77 changed the title Bump Tesla Fleet Api Bump Tesla Fleet API to v0.9.12 Mar 1, 2025
Copy link
Member

@frenck frenck left a comment

Choose a reason for hiding this comment

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

Thanks, @Bre77 👍

../Frenck

@frenck frenck added this to the 2025.3.0 milestone Mar 1, 2025
Copy link
Member

@frenck frenck left a comment

Choose a reason for hiding this comment

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

Hmm check-requirements seems to fail, can you take a look @Bre77?

../Frenck

@home-assistant home-assistant bot marked this pull request as draft March 1, 2025 12:08
@home-assistant
Copy link

home-assistant bot commented Mar 1, 2025

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

@Bre77 Bre77 marked this pull request as ready for review March 1, 2025 22:48
@home-assistant home-assistant bot requested a review from frenck March 1, 2025 22:48
@Bre77
Copy link
Contributor Author

Bre77 commented Mar 1, 2025

Test failure is now unrelated

Copy link
Member

@frenck frenck left a comment

Choose a reason for hiding this comment

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

Thanks, @Bre77 👍

../Frenck

@frenck frenck merged commit 3e93042 into home-assistant:dev Mar 1, 2025
41 of 42 checks passed
bramkragten pushed a commit that referenced this pull request Mar 2, 2025
* bump

* Update manifest.json

* Fix versions

* remove tesla_bluetooth

* Remove mistake
@github-actions github-actions bot locked and limited conversation to collaborators Mar 3, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants