From 41c1dd3c71b460c44c8bac96ef0a6bdc7693c72e Mon Sep 17 00:00:00 2001 From: Jamie Rasmussen Date: Thu, 17 Oct 2024 17:11:52 -0500 Subject: [PATCH] chore(weave): minor release note update --- dev_docs/RELEASE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dev_docs/RELEASE.md b/dev_docs/RELEASE.md index 6b7c4764362c..8c5611afa62f 100644 --- a/dev_docs/RELEASE.md +++ b/dev_docs/RELEASE.md @@ -12,7 +12,7 @@ This document outlines how to publish a new Weave release to our public [PyPI pa - Both of these commits will be pushed to master - Note: if you need to make a new minor or major release, you can do these steps manually with 2 PRs modifying the files in `weave/version.py` and `weave/pyproject.toml` -4. Go to the [publish-pypi-release](https://github.com/wandb/weave/actions/workflows/release.yaml) GitHub action and trigger a new release from the `x.y.z` branch (NOT MASTER). For riskier releases, make sure `Use Test PyPI` is checked so we first publish a test package. +4. Go to the [publish-pypi-release](https://github.com/wandb/weave/actions/workflows/release.yaml) GitHub action and trigger a new release from the `x.y.z` tag (NOT MASTER). For riskier releases, make sure `Use Test PyPI` is checked so we first publish a test package to [test.pypi.org](https://test.pypi.org/project/weave/#history). 5. Verify the new version of Weave exists in [PyPI](https://pypi.org/project/weave/) once it is complete.