@@ -157,15 +157,16 @@ In order to release a new version of Taskgraph, you will need to:
157157
1581581. Update ``CHANGELOG.md ``
1591592. Update ``version `` in ``pyproject.toml ``
160- 3. Commit, and land the above changes with a commit message like "chore: bump <version>"
161- 4. Draft a release in Github pointing to the above commit.
160+ 3. Run ``uv lock ``
161+ 4. Commit, and land the above changes with a commit message like "chore: bump <version>"
162+ 5. Draft a release in Github pointing to the above commit.
162163
163164 a. Create a new tag of the form ``X.Y.Z ``
164165 b. Ensure "Set as latest release" is checked
165166 c. Submit the release
166167
167- 5 . Wait for the ``pypi-publish `` Github workflow and ``push-image-decision `` task to finish.
168- 6 . Verify that expected version has been published to `pypi
168+ 6 . Wait for the ``pypi-publish `` Github workflow and ``push-image-decision `` task to finish.
169+ 7 . Verify that expected version has been published to `pypi
169170 <https://pypi.org/project/taskcluster-taskgraph> `__ and pushed to `DockerHub `_.
170171
171172.. _DockerHub : https://hub.docker.com/r/mozillareleases/taskgraph/tags
@@ -176,7 +177,7 @@ Releasing pytest-taskgraph
176177There's also a Pytest plugin packaged under ``packages/pytest-taskgraph ``. The
177178release process for this package is:
178179
179- 1. Update ``version `` in ``packages/pytest-taskgraph/pyproject.toml ``
180+ 1. Update ``version `` in ``packages/pytest-taskgraph/pyproject.toml ``, and run `` uv lock ``
1801812. Commit and land the changes with a commit message like "chore: bump pytest-taskgraph <version>"
1811823. Draft a release in Github pointing to the above commit.
182183
0 commit comments