Bump requests to 2.28.2

[mitch-dc]

Proposed change

• Bump of the requests dependency because of conflicts in other dependency.
• Changelog and diff from the dependency:
  • psf/requests@v2.28.1...v2.28.2
  • https://github.com/psf/requests/releases/tag/v2.28.2

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:

• Documentation added/updated for www.home-assistant.io

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:

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

[MartinHjelmare]

Please add a link to a changelog or GitHub commit compare view for the version bump in the PR description. Thanks!

[home-assistant]

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.

[MartinHjelmare]

Please add a link to a changelog or GitHub commit compare view for the version bump in the PR description. Thanks!

Please solve this too, thanks! ☝️

There are check boxes in the PR description to check off where this is requested too.

[mitch-dc]

Added psf/requests@v2.28.1...v2.28.2 to description

[MartinHjelmare]

We need to bump nuheat to 1.0.1 in a separate PR to solve the conflict for requests.

broox/python-nuheat@1.0.0...1.0.1

Can you do that? There are no logic changes in 1.0.1 besides the loosening of the requirement pinning for requests.

[mitch-dc]

1.0.1

#88958

[MartinHjelmare]

Have you tested an integration that uses requests with this version of requests in Home Assistant?

[mitch-dc]

Have you tested an integration that uses requests with this version of requests in Home Assistant?

Yes!

[MartinHjelmare]

Good!

[frenck]

Thanks, @mitch-dc 👍

../Frenck

[jonas-wilnerzon]

@MartinHjelmare @frenck In which upcoming release do you think this change will be included?

[MartinHjelmare]

At the moment it's targeted for the April release.

[jonas-wilnerzon]

@MartinHjelmare Alright, thanks!

[mitch-dc]

@MartinHjelmare Any posibillity to include in the next .1 release? It's breaking for a custom component that a lot of people use.
I'm working on making the component ready to include in core but time is not on my side.

https://github.com/mitch-dc/volkswagen_we_connect_id/issues

[MartinHjelmare]

Yes, we've tagged it for the next patch release now.