From ab38ddf64fd648695de1fa603181804b5aad3100 Mon Sep 17 00:00:00 2001 From: Sayak Paul Date: Wed, 27 Mar 2024 08:16:46 +0530 Subject: [PATCH] [chore] make the istructions on fetching all commits clearer. (#7474) * make the istructions on fetching all commits clearer. * Update setup.py Co-authored-by: YiYi Xu --------- Co-authored-by: YiYi Xu --- setup.py | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/setup.py b/setup.py index 84a98820f2..89bb1c9464 100644 --- a/setup.py +++ b/setup.py @@ -72,7 +72,11 @@ To create the package for PyPI. 9. Upload the final version to the actual PyPI: twine upload dist/* -r pypi -10. Prepare the release notes and publish them on GitHub once everything is looking hunky-dory. +10. Prepare the release notes and publish them on GitHub once everything is looking hunky-dory. You can use the following + Space to fetch all the commits applicable for the release: https://huggingface.co/spaces/lysandre/github-release. Repo should + be `huggingface/diffusers`. `tag` should be the previous release tag (v0.26.1, for example), and `branch` should be + the latest release branch (v0.27.0-release, for example). It denotes all commits that have happened on branch + v0.27.0-release after the tag v0.26.1 was created. 11. Run `make post-release` (or, for a patch release, `make post-patch`). If you were on a branch for the release, you need to go back to main before executing this.