.readthedocs.cfg vs Dashboard for Version Control

Managing Versioning Constraints

Read the Docs allows administrators to define the primary stable release and versioning behavior through two primary interfaces: the .readthedocs.cfg configuration file tracked in version control or the project dashboard settings.

When managing a project with frequent tag updates and a strict requirement for version-controlled infrastructure, there is a trade-off between the immediacy of dashboard overrides and the auditability of configuration files. Using the dashboard provides instant changes but creates a discrepancy between the repository state and the actual hosting behavior.

For a project targeting a specific stable branch across multiple environments, which approach ensures better consistency during automated VCS triggers?

• Does the .readthedocs.cfg file take precedence over dashboard settings during a webhook-triggered build?
• What are the implications for version stability when mixing these two configuration methods?