-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
pytest 6.2 release planning #8101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Sounds good! I meant to bring this up this week, but didn't have the time, thanks for stepping in. 👍 |
@pytestbot please prepare release from 6.2.x |
Found features or breaking changes in
|
@pytestbot please prepare release from master |
The request to prepare release
See: https://github.com/pytest-dev/pytest/actions/runs/417584552. |
@pytestbot please prepare release from master |
The request to prepare release
See: https://github.com/pytest-dev/pytest/actions/runs/417633005. |
The problem above is described in this commit message:
The fix in that commit is to use |
@pytestbot please prepare release from master |
As requested, opened a PR for release |
@bluetech let me do that release then right now |
@bluetech the release is now available in setuptools_scm 5.0.0 |
@RonnyPfannschmidt great, thanks. I figure that in order for CI to to pick it up I'll need to require it somewhere, or maybe it always picks the latest? Let me try. And there was also another problem in the PR pytestbot created that I need to take care of... I have thoroughly bad luck with pytest releases 😁 |
@RonnyPfannschmidt I can't quite get it to work, I'll leave it for the next time. For reference here's what I tried: diff --git a/pyproject.toml b/pyproject.toml
index dd4be6c22..444c92537 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -2,7 +2,7 @@
requires = [
# sync with setup.py until we discard non-pep-517/518
"setuptools>=42.0",
- "setuptools-scm[toml]>=3.4",
+ "setuptools-scm[toml]>=5.0",
"wheel",
]
build-backend = "setuptools.build_meta"
diff --git a/scripts/release.py b/scripts/release.py
index 798e42e1f..5bd8f9efb 100644
--- a/scripts/release.py
+++ b/scripts/release.py
@@ -63,7 +63,7 @@ def regen(version):
print(f"{Fore.CYAN}[generate.regen] {Fore.RESET}Updating docs")
check_call(
["tox", "-e", "regen"],
- env={**os.environ, "SETUPTOOLS_SCM_PRETEND_VERSION": version},
+ env={**os.environ, "SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST": version},
)
diff --git a/setup.cfg b/setup.cfg
index 09c07d5bb..70dd3703e 100644
--- a/setup.cfg
+++ b/setup.cfg
@@ -53,7 +53,7 @@ package_dir =
=src
setup_requires =
setuptools>=>=42.0
- setuptools-scm>=3.4
+ setuptools-scm>=5.0
zip_safe = no
[options.entry_points]
diff --git a/tox.ini b/tox.ini
index f0cfaa460..4107560d1 100644
--- a/tox.ini
+++ b/tox.ini
@@ -84,10 +84,7 @@ commands =
[testenv:regen]
changedir = doc/en
basepython = python3
-passenv = SETUPTOOLS_SCM_PRETEND_VERSION
-# TODO: When setuptools-scm 5.0.0 is released, use SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST
-# and remove the next line.
-install_command=python -m pip --use-deprecated=legacy-resolver install {opts} {packages}
+passenv = SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST
deps =
dataclasses
PyYAML
@@ -114,7 +111,7 @@ deps = -rtesting/plugins_integration/requirements.txt
setenv =
PYTHONPATH=.
# due to pytest-rerunfailures requiring 6.2+; can be removed after 6.2.0
- SETUPTOOLS_SCM_PRETEND_VERSION=6.2.0a1
+ SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST=6.2.0a1
commands =
pip check
pytest bdd_wallet.py |
@bluetech given this year i would consider it a plus if the bad luck falls onto releasing instead the rest of the hellscape Should I dig into the details tommorow to see if its a issue with pip or setuptools_scm? |
@RonnyPfannschmidt hehe
If you could check it that would be great, I assume there is some place else where the |
@pytestbot please prepare release from master |
As requested, opened a PR for release |
I'd like to release pytest 6.2 next Saturday (2020-12-12). Please let me know if you have any comments or reservations.
One thing is #7695, I plan to take care of it until then (probably by merging).
The text was updated successfully, but these errors were encountered: