Skip to content

Bump fyta_cli to 0.7.3 - #173784

Merged
joostlek merged 1 commit into
devfrom
frenck/bump-fyta-cli-0.7.3
Jun 15, 2026
Merged

Bump fyta_cli to 0.7.3#173784
joostlek merged 1 commit into
devfrom
frenck/bump-fyta-cli-0.7.3

Conversation

@frenck

@frenck frenck commented Jun 14, 2026

Copy link
Copy Markdown
Member

Proposed change

Bump fyta_cli from 0.7.2 to 0.7.3.

Upstream links:

Changes in 0.7.3:

The main fix corrects an inverted token expiration check that could cause unnecessary token refreshes or stale token usage. No changes needed on the Home Assistant side.

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

  • This PR fixes or closes issue: fixes #
  • This PR is related to issue:
  • Link to documentation pull request:
  • Link to developer documentation pull request:
  • Link to frontend pull request:

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 June 14, 2026 18:26
@home-assistant home-assistant Bot added cla-signed dependency Pull requests marked as a dependency upgrade integration: fyta small-pr PRs with less than 30 lines. labels Jun 14, 2026
@home-assistant

Copy link
Copy Markdown
Contributor

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

Code owner commands

Code owners of fyta 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 fyta 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.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

A straightforward dependency version bump of fyta_cli from 0.7.2 to 0.7.3 in the FYTA integration. The upstream fix corrects an inverted token expiration check that could cause unnecessary token refreshes or stale token usage. No Home Assistant-side code changes are required.

Changes:

  • Version string updated from 0.7.2 to 0.7.3 in manifest.json and requirements_all.txt

Reviewed changes

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

File Description
homeassistant/components/fyta/manifest.json Bumps fyta_cli requirement from 0.7.2 to 0.7.3
requirements_all.txt Updates the pinned fyta_cli version from 0.7.2 to 0.7.3

@dontinelli

Copy link
Copy Markdown
Contributor

The changes have no impact on the HA core integration (why I have not yet initiated a bump myself). But with the PR already prepared, I'm of course happy to approve. Thank you @frenck .

@joostlek
joostlek merged commit 2fd8222 into dev Jun 15, 2026
49 checks passed
@joostlek
joostlek deleted the frenck/bump-fyta-cli-0.7.3 branch June 15, 2026 10:53
@github-actions github-actions Bot locked and limited conversation to collaborators Jun 16, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

cla-signed code-owner-approved dependency Pull requests marked as a dependency upgrade integration: fyta Quality Scale: platinum small-pr PRs with less than 30 lines.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants