Prepare for 0.7.0 release

[BurnzZ]

PRs

• Provide a request fingerprinter for Scrapy 2.7+ #56
• Use custom download slots that bypass AutoThrottle #59

Checklist

• Update release date in CHANGES.rst
• Tag 0.7.0 after merging

[codecov]

Codecov Report

Merging #61 (152a8f0) into main (79cc82b) will decrease coverage by 2.52%.
The diff coverage is n/a.

❗ Current head 152a8f0 differs from pull request most recent head b5cfb5f. Consider uploading reports for the commit b5cfb5f to get more accurate results

@@            Coverage Diff             @@
##             main      #61      +/-   ##
==========================================
- Coverage   99.48%   96.96%   -2.53%     
==========================================
  Files           6        7       +1     
  Lines         388      395       +7     
==========================================
- Hits          386      383       -3     
- Misses          2       12      +10     

Impacted Files	Coverage Δ
scrapy_zyte_api/responses.py	92.06% <0.00%> (-7.94%)	⬇️
scrapy_zyte_api/_request_fingerprinter.py	89.47% <0.00%> (-7.90%)	⬇️
scrapy_zyte_api/__init__.py	71.42% <0.00%> (ø)

[wRAR]

"if they point" maybe?

[BurnzZ]

The new update on tox >= 4.0 had a lot of backward incompatible changes.

It's now strict on the testenv:<env_name> format which renders this old line to have this error:

pinned-26-scrapy: failed with env name pinned-scrapy-2.0 conflicting with base python python3.7
pinned-scrapy-2.0: FAIL code 1 (0.01 seconds)
evaluation failed :( (1.24 seconds)

Setting ignore_basepython_conflict=True is supposed to fix this but it doesn't work. Seems like they're still releasing a lot of regression fixes after the 4.0 release.

They're also quite aggressive on the name inference. If they see any two digits in the env name, they'd treat it as a Python version. So other workarounds like 20, 2-0, etc doesn't work.