Skip to content

Bump aiotractive to 1.0.3#169059

Merged
joostlek merged 1 commit into
home-assistant:devfrom
bieniu:aiotractive-1.0.3
Apr 24, 2026
Merged

Bump aiotractive to 1.0.3#169059
joostlek merged 1 commit into
home-assistant:devfrom
bieniu:aiotractive-1.0.3

Conversation

@bieniu
Copy link
Copy Markdown
Member

@bieniu bieniu commented Apr 24, 2026

Breaking change

Proposed change

Release note: https://github.com/zhulik/aiotractive/releases/tag/v1.0.3
Diff: zhulik/aiotractive@v1.0.2...v1.0.3

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

  • I understand the code I am submitting and can explain how it works.
  • 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.
  • Any generated code has been carefully reviewed for correctness and compliance with project standards.

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 diff between library versions and ideally a link to the changelog/release notes is added to the PR description.

To help with the load of incoming pull requests:

Copilot AI review requested due to automatic review settings April 24, 2026 12:43
@bieniu bieniu requested a review from Danielhiversen as a code owner April 24, 2026 12:43
@home-assistant home-assistant Bot added cla-signed dependency Pull requests marked as a dependency upgrade integration: tractive small-pr PRs with less than 30 lines. labels Apr 24, 2026
@home-assistant
Copy link
Copy Markdown
Contributor

Hey there @Danielhiversen, @zhulik, mind taking a look at this pull request as it has been labeled with an integration (tractive) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of tractive can trigger bot actions by commenting:

  • @home-assistant close Closes the pull request.
  • @home-assistant mark-draft Mark the pull request as draft.
  • @home-assistant ready-for-review Remove the draft status from the pull request.
  • @home-assistant rename Awesome new title Renames the pull request.
  • @home-assistant reopen Reopen the pull request.
  • @home-assistant unassign tractive Removes the current integration label and assignees on the pull request, add the integration domain after the command.
  • @home-assistant update-branch Update the pull request branch with the base branch.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) to the pull request.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) on the pull request.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Updates the Tractive integration’s pinned aiotractive dependency to incorporate upstream fixes (per v1.0.3 release notes), which may address reported device tracker issues.

Changes:

  • Bump aiotractive from 1.0.2 to 1.0.3 in the Tractive integration manifest.
  • Update the pinned version in requirements_all.txt and requirements_test_all.txt to keep dependency sets consistent.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File Description
homeassistant/components/tractive/manifest.json Pins Tractive integration requirement to aiotractive==1.0.3.
requirements_all.txt Updates global runtime requirements pin for aiotractive to 1.0.3.
requirements_test_all.txt Updates test requirements pin for aiotractive to 1.0.3.

@bieniu bieniu added this to the 2026.4.4 milestone Apr 24, 2026
@joostlek joostlek merged commit bb95208 into home-assistant:dev Apr 24, 2026
52 checks passed
frenck pushed a commit that referenced this pull request Apr 24, 2026
@frenck frenck mentioned this pull request Apr 24, 2026
@github-actions github-actions Bot locked and limited conversation to collaborators Apr 25, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants