RomanNum3ral
/
scrapy
mirror of https://github.com/scrapy/scrapy.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updated Scrapy release procedure (markdown)

Andrey Rakhmatullin 2024-11-18 16:10:05 +05:00
parent 95ecfe9a18
commit 1e8f21bd76
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
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.