[Bug]: custom integration 'localtuya' sets "version" directly to update a config entry

[mocarela]

LocalTuya Version

3.2.5.2

Home Assistant Version

2024.3.1

Environment

• Does the device work using the Home Assistant Tuya Cloud component?
• Is this device connected to another local integration, including Home Assistant and any other tools?
• The devices are within the same HA subnet, and they get discovered automatically when I add them

What happened?

Two warnings in the logs on each HA start.

Steps to reproduce.

1. Stop HA container
2. Add integration in custom_components
3. Start HA container

Relevant log output

2024-05-05 14:09:24.395 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'localtuya' sets "version" directly to update a config entry. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to use async_update_entry instead at custom_components/localtuya/__init__.py, line 287: config_entry.version = 4, please create a bug report at https://github.com/xZetsubou/hass-localtuya/issues

Diagnostics information.

No response

[xZetsubou]

What is that warning 😸 I'm on HA 2024.5.0b1 and never seen this warning before. I'll look into this however not sure if it's bugged for 2024.3.1 or not.

edit: no wonder this didn't shows up I think it because it you probably just installed this fork and the entry migrate updated the config entry.

[github-actions]

This issue was closed because it was resolved on the release: