Update dependency pytest-postgresql to v6 #1051
Merged
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
->^4.1.1 || ^5.0.0 || ^6.0.0
Release Notes
ClearcodeHQ/pytest-postgresql (pytest-postgresql)
v6.0.0
Compare Source
==================
Breaking changes
#​899 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/899>
__)Bugfixes
DepcrecationWarning
fordatetime.datetime.utcnow
on Python 3.12. (#​896 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/896>
__)Deprecations
Developers are encouraged to either use the load function/parameter
for process fixture, or create an intermediate fixture placed between client
and tests themselves to fill in the data. (
#​850 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/850>
__)Features
Now all sql files used to initialise database for tests, has to be passed as pathlib.Path instance.
This helps the DatabaseJanitor choose correct behaviour based on parameter. (
#​638 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/638>
__)Have separate parameters for template database name and database name in DatabaseJanitor.
It'll make it much clearer to understand the code and Janitor's behaviour. (
#​672 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/672>
__)Template databases are now created with is_template flag turned on, and not by setting allow_connections to false.
The allow_connections flag being set to false is used strictly right before we attempt to drop the database. (
#​914 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/914>
__)Miscellaneus
#​865 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/865>
,#​882 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/882>
,#​893 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/893>
,#​900 <https://github.com/ClearcodeHQ/pytest-postgresql/issues/900>
Configuration
📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" (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 has been generated by Mend Renovate. View repository job log here.