Prepare release 7.2.0 #10412
Prepare release 7.2.0 #10412
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
| @@ -1963,7 +1960,7 @@ All the command-line flags can be obtained by running ``pytest --help``:: | |||
| Default marker for empty parametersets | |||
| norecursedirs (args): Directory patterns to avoid for recursion | |||
| testpaths (args): Directories to search for tests when no files or | |||
| directories are given in the command line | |||
| directories are given on the command line | |||
There was a problem hiding this comment.
hmm, this looks like we might have had some typo fixes in places where its not helpfull
There was a problem hiding this comment.
What do you mean, is there a problem with those changes?
There was a problem hiding this comment.
actually i think i missread the diff
we might want to make regendoc a regular check for the branches to open regendoc fixup prs
There was a problem hiding this comment.
Yeah... in fact, we could make an action that runs anytime a PR is opened or pushed to: it would run regendoc, and push a new commit if any .rst files have changed.
There was a problem hiding this comment.
that unfortunately can't be done safely without exposing privileged credentials to the pull request code or using a third party app to do the pushing
There was a problem hiding this comment.
@asottile would it be safe enough safe, i we would have to trigger an actual workflow action on main with the pr as parameter (similar to the create pr workflow)
that way the pr code would work similar to the workflow for creating a release
another alternative would be to just always have a release pr on standby (instead of manually triggering them) and using them as indicator
|
@nicoddemus for practical reasons i'll defer pulling the trigger to when i get into office tommorow morning |
|
Sure thing. 👍 Thanks for taking care of this release. |
| - `#10218 <https://github.com/pytest-dev/pytest/issues/10218>`_: ``@pytest.mark.parametrize()`` (and similar functions) now accepts any ``Sequence[str]`` for the argument names, | ||
| instead of just ``list[str]`` and ``tuple[str, ...]``. |
There was a problem hiding this comment.
this doesn't seem to go to the right place
|
gone with a signed tag will merge after release |
Prepare release 7.2.0 (cherry picked from commit ac4e3cc)
Prepare release 7.2.0 (cherry picked from commit ac4e3cc)
|
Was 7.2.0 announced on Twitter? |
Looks like it was in the meantime! (retweeted by |
Created automatically from manual trigger.
Once all builds pass and it has been approved by one or more maintainers, the build
can be released by pushing a tag
7.2.0to this repository.