@@ -17,8 +17,8 @@ Version Bump and Dependency Updates
1717 - ``conda_package/mpas_tools/__init__.py ``
1818 - ``conda_package/recipe/recipe.yaml ``
1919
20- - Make sure the version follows semantic versioning (see
21- https://semver.org/) .
20+ - Make sure the version follows
21+ ` semantic versioning < https://semver.org/ >`_ .
2222 For release candidates, use versions like ``1.3.0rc1 `` (no ``v `` prefix).
2323
24242. **Check and Update Dependencies **
@@ -38,7 +38,7 @@ Version Bump and Dependency Updates
3838 - The dependencies in ``recipe.yaml `` are the ones that will be used for the
3939 released package on conda-forge. The dependencies in ``pyproject.toml ``
4040 are for PyPI and should be kept in sync as much as possible but are only
41- there as a sanity check when we run ``` pip check ``. The ``dev-spec.txt ``
41+ there as a sanity check when we run ``pip check ``. The ``dev-spec.txt ``
4242 file should include all dependencies needed for development and testing,
4343 and ``pixi.toml `` should remain equivalent for pixi users.
4444
@@ -100,8 +100,7 @@ Tagging and Publishing a Release Candidate
100100 - Update dependencies if needed
101101
102102 - Commit, push to a new branch, and open a PR **against the ``dev`` branch **
103- of the feedstock:
104- https://github.com/conda-forge/mpas_tools-feedstock
103+ of the `mpas_tools-feedstock <https://github.com/conda-forge/mpas_tools-feedstock >`_.
105104
106105 - Follow any instructions in the PR template and merge once approved
107106
@@ -112,7 +111,7 @@ Publishing a Stable Release
112111
113112 - For stable releases, create a GitHub release page as follows:
114113
115- - Go to https://github.com/MPAS-Dev/MPAS-Tools/releases
114+ - Go to ` the GitHub releases page < https://github.com/MPAS-Dev/MPAS-Tools/releases >`_
116115
117116 - Click "Draft a new release"
118117
@@ -127,8 +126,8 @@ Publishing a Stable Release
127126
1281277. **Updating the conda-forge Feedstock for a Stable Release **
129128
130- - Wait for the ``regro-cf-autotick-bot `` to open a PR at:
131- https://github.com/conda-forge/mpas_tools-feedstock
129+ - Wait for the ``regro-cf-autotick-bot `` to open a PR at the
130+ ` mpas_tools-feedstock repository < https://github.com/conda-forge/mpas_tools-feedstock >`_.
132131
133132 - This may take several hours to a day.
134133
@@ -137,7 +136,8 @@ Publishing a Stable Release
137136 - Merge once CI checks pass
138137
139138 **Note: ** If you are impatient, you can accelerate this process by creating
140- a bot issue at: https://github.com/conda-forge/mpas_tools-feedstock/issues
139+ a bot issue at the
140+ `mpas_tools-feedstock issues page <https://github.com/conda-forge/mpas_tools-feedstock/issues >`_
141141 with the subject ``@conda-forge-admin, please update version ``. This
142142 will open a new PR with the version within a few minutes.
143143
0 commit comments