Update voluptuous to 0.15.2

[cdce8p]

Proposed change

Replaces #120268
alecthomas/voluptuous@0.13.1...0.15.2
https://github.com/alecthomas/voluptuous/releases/tag/0.15.1
https://github.com/alecthomas/voluptuous/releases/tag/0.15.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
• 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.

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.

[bdraco]

  raise er.MultipleInvalid(errors)
voluptuous.error.MultipleInvalid: not a valid value @ data['name_raw']

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/runner/work/core/core/homeassistant/components/snips/__init__.py", line 149, in message_received
    intent_response = await intent.async_handle(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/work/core/core/homeassistant/helpers/intent.py", line 143, in async_handle
    raise InvalidSlotInfo(f"Received invalid slot info for {intent_type}") from err
homeassistant.helpers.intent.InvalidSlotInfo: Received invalid slot info for Lights

Looks like it might be an actual regression?

[epenet]

Marked as draft as the test failure is related to the PR.

[cdce8p]

Looks like it might be an actual regression?

Yes. Fix in alecthomas/voluptuous#522

[bdraco]

Probably should merge in dev again before merging in case there are new places that need fixes

[cdce8p]

Probably should merge in dev again before merging in case there are new places that need fixes

Just did a rebase with force-push. Unless the latest one or two commits contain breaking changes, we should be good here.

[bdraco]

Tested on production x2. All good afaict

[bdraco]

Thanks @cdce8p

[bdraco]

Cla bot check seems stuck

Will close reopen and merge to see if it will clear

[bdraco]

Looks ok now.

[bdraco]

Nice. This will help mqtt startup time