Skip to content
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.

Sign up for GitHub

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

Jump to bottom

fix(deps): update all dependencies #106

Closed
wants to merge 1 commit into from
Closed

fix(deps): update all dependencies #106

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 15, 2023 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
peewee 3.15.4 -> 3.16.0 age adoption passing confidence
psycopg2-binary (source, changelog) 2.9.5 -> 2.9.6 age adoption passing confidence
pytest (source, changelog) 7.2.1 -> 7.2.2 age adoption passing confidence
ruff 0.0.223 -> 0.0.260 age adoption passing confidence

Release Notes

coleifer/peewee

v3.16.0

Compare Source

This release contains backwards-incompatible changes in the way Peewee
initializes connections to the underlying database driver. Previously, peewee
implemented autocommit semantics on-top of the existing DB-API transactional
workflow. Going forward, Peewee instead places the DB-API driver into
autocommit mode directly.

Why this change?

Previously, Peewee emulated autocommit behavior for top-level queries issued
outside of a transaction. This necessitated a number of checks which had to be
performed each time a query was executed, so as to ensure that we didn't end up
with uncommitted writes or, conversely, idle read transactions. By running the
underlying driver in autocommit mode, we can eliminate all these checks, since
we are already managing transactions ourselves.

Behaviorally, there should be no change -- Peewee will still treat top-level
queries outside of transactions as being autocommitted, while queries inside of
atomic() / with db: blocks are implicitly committed at the end of the
block, or rolled-back if an exception occurs.

How might this affect me?

  • If you are using the underlying database connection or cursors, e.g. via
    Database.connection() or Database.cursor(), your queries will now be
    executed in autocommit mode.
  • The commit= argument is deprecated for the cursor(), execute() and
    execute_sql() methods.
  • If you have a custom Database implementation (whether for a database that
    is not officially supported, or for the purpose of overriding default
    behaviors), you will want to ensure that your connections are opened in
    autocommit mode.

Other changes:

  • Some fixes to help with packaging in Python 3.11.
  • MySQL get_columns() implementation now returns columns in their declared
    order.

View commits

pytest-dev/pytest

v7.2.2

Compare Source

pytest 7.2.2 (2023-03-03)

Bug Fixes

  • #​10533: Fixed pytest.approx{.interpreted-text role="func"} handling of dictionaries containing one or more values of [0.0]{.title-ref}.
  • #​10592: Fixed crash if [--cache-show]{.title-ref} and [--help]{.title-ref} are passed at the same time.
  • #​10597: Fixed bug where a fixture method named teardown would be called as part of nose teardown stage.
  • #​10626: Fixed crash if --fixtures and --help are passed at the same time.
  • #​10660: Fixed :pypytest.raises{.interpreted-text role="func"} to return a 'ContextManager' so that type-checkers could narrow
    pytest.raises(...) if ... else nullcontext() down to 'ContextManager' rather than 'object'.

Improved Documentation

  • #​10690: Added [CI]{.title-ref} and [BUILD_NUMBER]{.title-ref} environment variables to the documentation.
  • #​10721: Fixed entry-points declaration in the documentation example using Hatch.
  • #​10753: Changed wording of the module level skip to be very explicit
    about not collecting tests and not executing the rest of the module.
charliermarsh/ruff

v0.0.260

Compare Source

What's Changed

Rules
Bug Fixes

New Contributors

Full Changelog: astral-sh/ruff@v0.0.259...v0.0.260

v0.0.259

Compare Source

Summary

Follow-up release to v0.0.258 to fix an issue related to rule resolution via select and ignore.

What's Changed

Bug Fixes

Full Changelog: astral-sh/ruff@v0.0.258...v0.0.259

v0.0.258

Compare Source

What's Changed

Rules
Bug Fixes

New Contributors

Full Changelog: astral-sh/ruff@v0.0.257...v0.0.258

v0.0.257

Compare Source

What's Changed

Rules
Bug Fixes

New Contributors

Full Changelog: astral-sh/ruff@v0.0.256...v0.0.257

v0.0.256

Compare Source

What's Changed

Bug Fixes
Other Changes

Full Changelog: astral-sh/ruff@v0.0.255...v0.0.256

v0.0.255

Compare Source

What's Changed

Rules
Settings
Bug Fixes

New Contributors

Full Changelog: astral-sh/ruff@v0.0.254...v0.0.255

v0.0.254

Compare Source

What's Changed

Rules
CLI
Settings
Bug Fixes

New Contributors

Full Changelog: astral-sh/ruff@v0.0.253...v0.0.254

v0.0.253

Compare Source

What's Changed

Rules
Settings
Bug Fixes

New Contributors

Full Changelog: astral-sh/ruff@v0.0.252...v0.0.253

v0.0.252

Compare Source

What's Changed

Rules
Bug Fixes

New Contributors

Full Changelog: astral-sh/ruff@v0.0.251...v0.0.252

v0.0.251

[Compare

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/all-major-minor-patch branch 3 times, most recently from e832ca8 to 44fa2e6 Compare March 23, 2023 22:01
@renovate renovate bot force-pushed the renovate/all-major-minor-patch branch 4 times, most recently from f02ce91 to cc07c4f Compare April 5, 2023 07:57
@renovate renovate bot force-pushed the renovate/all-major-minor-patch branch 2 times, most recently from b254aae to db3be84 Compare April 14, 2023 21:34
@renovate renovate bot force-pushed the renovate/all-major-minor-patch branch 4 times, most recently from 8b5f6ea to 5a15ba0 Compare April 25, 2023 11:29
@renovate renovate bot force-pushed the renovate/all-major-minor-patch branch 2 times, most recently from 759fb8d to dbcc6c9 Compare May 5, 2023 20:39
@renovate renovate bot force-pushed the renovate/all-major-minor-patch branch from dbcc6c9 to b7d26d6 Compare May 8, 2023 07:31
@github-actions
Copy link

This PR has been open for 7 days with no activity. Remove the stale label or add a comment or it will be closed in 3 days.

@github-actions github-actions bot added the Stale label May 16, 2023
@github-actions
Copy link

This PR was closed because it has been stalled for 10 days with no activity.

@github-actions github-actions bot closed this May 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
Stale
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants