Use VERSION from PrusaLinkConfigFlow in prusalink

[heikkih]

Proposed change

Fixes a latent bug in the migration version check.

__init__.py and test_init.py both did:

from homeassistant.components.prusalink.config_flow import ConfigFlow
...
config_entry.version > ConfigFlow.VERSION

…but ConfigFlow here is homeassistant.config_entries.ConfigFlow (HA's base class, re-exported via our config_flow module), not the integration's actual subclass PrusaLinkConfigFlow. So the comparison reads HA's default VERSION = 1, not ours.

This works today by coincidence because both happen to be 1. The check becomes silently wrong the moment PrusaLinkConfigFlow.VERSION is ever bumped: migration would refuse to load valid config entries created by the new code, and the test_migration_fails_on_future_version test would no longer be testing a "future" version.

While in there, the future-version guard now also covers minor_version — it compares (version, minor_version) as a tuple against the class constants, so a downgraded install can't accidentally accept entries created by a newer minor version. A regression test exercises the new branch.

Note

There's no plan to bump PrusaLinkConfigFlow.VERSION right now — this is just removing a latent footgun before it bites.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New feature (thank you!)
• Breaking change (non-breaking change which fixes an issue)
• Code quality improvements to existing code or addition of tests

Checklist

• The code change is tested and works locally
• Local tests pass (9 passed in tests/components/prusalink/test_init.py)
• Lint (ruff) and mypy pass
• There is no commented out code in this PR

[Copilot]

Pull request overview

This PR fixes a latent migration-version check bug in the prusalink integration by ensuring comparisons use the integration’s actual config flow class (PrusaLinkConfigFlow) rather than Home Assistant’s base ConfigFlow.

Changes:

• Update the migration “future version” guard in async_migrate_entry to reference PrusaLinkConfigFlow.VERSION.
• Update the migration regression test to reference PrusaLinkConfigFlow.VERSION so it remains meaningful if the integration’s version is bumped later.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
homeassistant/components/prusalink/__init__.py	Use the integration’s config flow VERSION for the migration downgrade guard.
tests/components/prusalink/test_init.py	Align the “future version” migration test with the integration’s config flow VERSION.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.

[abmantis]

Thanks!