Don't start recorder if a database from the future is used

[emontnemery]

Proposed change

Don't start recorder if a database from the future is used

This prevents a migrated database to be used by a version of Home Assistant which does not support it.
Without this check, the database may end up in an undefined state after downgrade.

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.

To help with the load of incoming pull requests:

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

[home-assistant]

Hey there @home-assistant/core, mind taking a look at this pull request as it has been labeled with an integration (recorder) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of recorder 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 recorder 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.

[frenck]

Thanks, @emontnemery 👍

../Frenck

[balloob]

Do we need to mention Core ?

Suggested change

	"Home Assistant Core supports (%s), either upgrade Home Assistant Core "
	"Home Assistant supports (%s), either upgrade Home Assistant "

[emontnemery]

I think so, the database is tied to the core version, and we take care to talk about the Home Assistant Core version in other cases.

[emontnemery]

If this proves to create trouble for users, we can introduce the concept of minor database schema versions, where we allow using a future minor version.

[frenck]

If this proves to create trouble for users, we can introduce the concept of minor database schema versions, where we allow using a future minor version.

Yeah I like that approach. But let's go down that path when needed / it arrises.