Migrate slack to use the latest version available from Slack. The way we currently upload files via the notify service will break in March 2025. This PR comes before the actual fix for that. Blocking calls are currently being made within the dependency during file upload. So that will take some more work.
Hey there @fletcherau, mind taking a look at this pull request as it has been labeled with an integration (slack) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of `slack` can trigger bot actions by commenting:
- `@home-assistant close` Closes the pull request.
- `@home-assistant rename Awesome new title` Renames the pull request.
- `@home-assistant reopen` Reopen the pull request.
- `@home-assistant unassign slack` Removes the current integration label and assignees on the pull request, add the integration domain after the command.
- `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
- `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.
Proposed change
Migrate slack to use the latest version available from Slack. The way we currently upload files via the notify service will break in March 2025. This PR comes before the actual fix for that. Blocking calls are currently being made within the dependency during file upload. So that will take some more work.
https://github.com/slackapi/python-slack-sdk/compare/2.5.0...v3.27.1
Type of change
Additional information
Checklist
ruff format homeassistant tests
)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest
.requirements_all.txt
.Updated by running
python3 -m script.gen_requirements_all
..coveragerc
.To help with the load of incoming pull requests: