From 1e8f21bd76ba20da4e3767d8a7bca7eba12e3a9c Mon Sep 17 00:00:00 2001 From: Andrey Rakhmatullin Date: Mon, 18 Nov 2024 16:10:05 +0500 Subject: [PATCH] Updated Scrapy release procedure (markdown) --- Scrapy-release-procedure.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Scrapy-release-procedure.md b/Scrapy-release-procedure.md index 31fb4da..8f1da0a 100644 --- a/Scrapy-release-procedure.md +++ b/Scrapy-release-procedure.md @@ -120,7 +120,7 @@ as follows: 1. Update the `version` string. -2. Update the `sha256sum` from the PyPI's [source release +2. Update the `sha256sum` and `blake2b256` values from the PyPI's [source release tarball](https://pypi.org/project/Scrapy/#files). 3. Reset the `build/number` to `0`. This number is only increased when we @@ -150,6 +150,6 @@ As a different team produces images for [Scrapy Cloud stacks](https://github.com To avoid the risk of CI suddenly failing and confusing pull request authors, we freeze some CI packages in `tox.ini`, `tests/requirements.txt`, and `.pre-commit-config.yaml`. -In `tox.ini` and `tests/requirements.txt` tou can find them looking for `==`, but mind that some freezes are to be kept (e.g. to test minimum versions of Scrapy dependencies). +In `tox.ini` and `tests/requirements.txt` you can find them looking for `==`, but mind that some freezes are to be kept (e.g. to test minimum versions of Scrapy dependencies). Right after a major or minor release would be a good time to update those packages, solving or allow-listing any issue raised by their new versions. \ No newline at end of file