Description

I noticed a synchronization issue regarding theschema.json update and the actual build environment support for Python 3.14.

Previously, I encountered build errors when trying to use Python3.14, even though it was already listed as valid in theschema file.
It works now, but there was atime lag (whether hours or days) between the schema update in this repository and the actual infrastructure support.

Impact

We useRenovate to automate our dependency updates based on your schema.

1. Renovate detected the change inschema.json (allowing3.14) immediately after it was merged into themain branch.
2. It opened a PR to update our configuration (e.g.,chore(deps): update dependency python to v3.14 Flexget/Flexget#4679).
3. The PR checks failed because the Read the Docs build servers had not yet been deployed with the new version support at that specific moment.

Hypothesis

I suspect this happens because theschema.json lives in the source code repository. When a PR merging support for a new Python version is merged, the schema updates immediately on GitHub, but there is a delay before that code is deployed to the production build servers.

Suggestion

Publish the official schema to a live URL (e.g., on docs.readthedocs.io or an API endpoint) representing thecurrent production state.

If we could point Renovate to a URL that is only updatedafter (or during) the production deployment, it would ensure the schema is neverahead of the actual build capabilities. Relying on the file in themain branch of the source repo seems to be the root cause of these premature PRs.