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

Update geopy to 2.3.0 #82145

Merged
merged 1 commit into from Nov 15, 2022
Merged

Update geopy to 2.3.0 #82145

merged 1 commit into from Nov 15, 2022

Conversation

frenck
Copy link
Member

@frenck frenck commented Nov 15, 2022

Proposed change

Updates geopy to 2.3.0; providing Python 3.11 support
Release notes: https://github.com/geopy/geopy/releases/tag/2.3.0

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:

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
  • The code has been formatted using Black (black --fast 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.
  • Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

@home-assistant
Copy link

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

Code owner commands

Code owners of aprs can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Change the title of the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign aprs Removes the current integration label and assignees on the issue, add the integration domain after the command.

@frenck frenck added the smash Indicator this PR is close to finish for merging or closing label Nov 15, 2022
@PhilRW
Copy link
Contributor

PhilRW commented Nov 15, 2022

A brief look at their changelog doesn't seem to indicate anything breaking.... I guess we'll see. :)

@frenck frenck merged commit a2e6383 into dev Nov 15, 2022
@frenck frenck deleted the frenck-2022-2092 branch November 15, 2022 20:52
@github-actions github-actions bot locked and limited conversation to collaborators Nov 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cla-signed dependency dependency-bump integration: aprs Quality Scale: No score small-pr PRs with less than 30 lines. smash Indicator this PR is close to finish for merging or closing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants