Mention package metadata files as well
@@ -443,6 +443,10 @@ Configuration for Sphinx documentation
If you want to pin Sphinx to a specific version,
use a ``requirements.txt`` or ``environment.yml`` file
(see :ref:`config-file/v2:requirements file` and :ref:`config-file/v2:conda.environment`).
+ If you are using a metadata file to describe code dependencies
+ like ``setup.py``, ``pyproject.toml``, or similar,
+ you can use the ``extra_requirements`` option
+ (see :ref:`config-file/v2:packages`).
This also allows you to override :ref:`the default pinning done by Read the Docs
if your project was created before October 2020 <builds:external dependencies>`.
@@ -497,6 +501,10 @@ Configuration for MkDocs documentation.
If you want to pin MkDocs to a specific version,
use a ``requirements.txt`` or ``environment.yml`` file
(see :ref:`config-file/v2:requirements file` and :ref:`config-file/v2:conda.environment`).
+ If you are using a metadata file to describe code dependencies
+ like ``setup.py``, ``pyproject.toml``, or similar,
+ you can use the ``extra_requirements`` option
+ (see :ref:`config-file/v2:packages`).
This also allows you to override :ref:`the default pinning done by Read the Docs
if your project was created before March 2021 <builds:external dependencies>`.
