Update dependency pytest-postgresql to v7 #1128
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^4.1.1 || ^5.0.0 || ^6.0.0
->^4.1.1 || ^5.0.0 || ^6.0.0 || ^7.0.0
Release Notes
dbfixtures/pytest-postgresql (pytest-postgresql)
v7.0.0
Compare Source
==================
Breaking changes
#​1087 <https://github.com/dbfixtures/pytest-postgresql/issues/1087>
__)Bugfixes
Passing all environment variables to the initdb.
This helps the cases where og_ctl is replaced by custom shell script
making additional calls, and needs all the variables, that ie server process gets. (
#​1076 <https://github.com/dbfixtures/pytest-postgresql/issues/1076>
__)Features
If a test run ended in an error that prevented proper test cleanup,
developer can now use
--postgresql-drop-test-database
command line flag,to delete database from noproc fixture at the start. (
#​265 <https://github.com/dbfixtures/pytest-postgresql/issues/265>
__)DatabaseJanitor.cursor now accepts optional parameter dbname, which defaults to
postgres
This database name is used to make connection to and return a cursor. (
#​265 <https://github.com/dbfixtures/pytest-postgresql/issues/265>
__)When running tests with xdist, pytest-postgresql now attempts to detect random ports
selected by other nodes by writing down a .port file in session temporary directory.
The number of tries it attempts to select unused port is configurable,
and defaults to 0.
In case pytest-postgresql won't be able to select unused port,
PortForException is thrown with appropriate message. (
#​872 <https://github.com/dbfixtures/pytest-postgresql/issues/872>
__)Mark Python 3.13 as supported.
Miscellaneus
#​707 <https://github.com/dbfixtures/pytest-postgresql/issues/707>
,#​895 <https://github.com/dbfixtures/pytest-postgresql/issues/895>
,#​1047 <https://github.com/dbfixtures/pytest-postgresql/issues/1047>
,#​1048 <https://github.com/dbfixtures/pytest-postgresql/issues/1048>
,#​1055 <https://github.com/dbfixtures/pytest-postgresql/issues/1055>
,#​1061 <https://github.com/dbfixtures/pytest-postgresql/issues/1061>
,#​1062 <https://github.com/dbfixtures/pytest-postgresql/issues/1062>
,#​1063 <https://github.com/dbfixtures/pytest-postgresql/issues/1063>
,#​1081 <https://github.com/dbfixtures/pytest-postgresql/issues/1081>
__maxsplit
has beenformally deprecated.
Update code to use keyword argument
maxsplit
instead of positional.Configuration
📅 Schedule: Branch creation - "* 0-4,22-23 * * 1-5,* * * * 0,6" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.