Skip to content

Bump pytrydan to 1.0.3 - #175486

Merged
zweckj merged 1 commit into
devfrom
claude/pytrydan-v1-0-3-bump-geptao
Jul 3, 2026
Merged

Bump pytrydan to 1.0.3#175486
zweckj merged 1 commit into
devfrom
claude/pytrydan-v1-0-3-bump-geptao

Conversation

@balloob

@balloob balloob commented Jul 3, 2026

Copy link
Copy Markdown
Member

Breaking change

Proposed change

Bumps pytrydan from 1.0.2 to 1.0.3 for the V2C integration.

This release loosens pytrydan's dependency on tenacity, whose previously pinned version was blocking other integrations from resolving their own tenacity requirements.

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:

  • I have reviewed two other open pull requests in this repository.

🤖 Generated with Claude Code

https://claude.ai/code/session_01MY8df4sgubJrnBk2Zisqn4


Generated by Claude Code

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MY8df4sgubJrnBk2Zisqn4
Copilot AI review requested due to automatic review settings July 3, 2026 11:41
@balloob
balloob requested a review from dgomes as a code owner July 3, 2026 11:41
@home-assistant home-assistant Bot added dependency Pull requests marked as a dependency upgrade integration: v2c small-pr PRs with less than 30 lines. labels Jul 3, 2026
@home-assistant

home-assistant Bot commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

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

Code owner commands

Code owners of v2c 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 v2c 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

This PR bumps the pytrydan library from 1.0.2 to 1.0.3 for the V2C integration. According to the PR description, the new release loosens pytrydan's pin on tenacity, which was preventing other integrations from resolving their own tenacity requirements. The upstream release v1.0.3 (published 2026-07-02) was verified to exist and only contains a bug fix and formatting changes.

Changes:

  • Bump pytrydan to 1.0.3 in the V2C integration manifest.
  • Regenerate requirements_all.txt to match the new version.

Reviewed changes

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

File Description
homeassistant/components/v2c/manifest.json Updates the pytrydan requirement pin to 1.0.3.
requirements_all.txt Regenerated dependency list reflecting pytrydan==1.0.3.

The change is minimal, self-consistent across both files, contains no unrelated modifications, and the target version is confirmed to exist upstream.

@github-actions

github-actions Bot commented Jul 3, 2026

Copy link
Copy Markdown

Check requirements

Checked at commit 3dd667d.

⚠️ Some checks require attention — see the details below.

Package Old New No Advisories Not Yanked Repo Public CI Upload Release Pipeline Security PR Link Async Safe
pytrydan 1.0.2 1.0.3 ⚠️ ⚠️ ☑️
📦 pytrydan: 1.0.2 → 1.0.3
  • No Advisories: ✅ No active advisories reported by PyPI for version 1.0.3.
  • Not Yanked: ✅ Version 1.0.3 is a live (non-yanked) release.
  • Repo Public: ✅ https://github.com/dgomes/pytrydan is publicly accessible.
  • CI Upload: ⚠️ No PEP 740 provenance attestation present on PyPI. Upload method cannot be verified from PyPI alone.
  • Release Pipeline: ⚠️ Publishes via pypa/gh-action-pypi-publish with a static PYPI_TOKEN on push to main (not OIDC); environment: release guard is present.
  • Security: ☑️ Baseline scan found nothing obvious in pyproject.toml, src/pytrydan/__init__.py, src/pytrydan/trydan.py. This is not a security review — only the cheap checks were run.
  • PR Link: ✅ PR description links to dgomes/pytrydan@v1.0.2...v1.0.3 covering both versions.
  • Async Safe: ✅ No new blocking calls introduced in 1.0.2 → 1.0.3.

Generated by Check requirements (AW) · 100.2 AIC · ⌖ 14.2 AIC · ⊞ 29.9K ·

@zweckj
zweckj merged commit 1304c29 into dev Jul 3, 2026
50 checks passed
@zweckj
zweckj deleted the claude/pytrydan-v1-0-3-bump-geptao branch July 3, 2026 12:20
@github-actions github-actions Bot locked and limited conversation to collaborators Jul 4, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

dependency Pull requests marked as a dependency upgrade integration: v2c Quality Scale: No score small-pr PRs with less than 30 lines.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants