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.

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

chore(deps): update mend: high confidence minor and patch dependency updates #70

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

mend-for-github-com[bot]
Copy link

@mend-for-github-com mend-for-github-com bot commented Feb 28, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
bandit (source, changelog) 1.7.1 -> 1.7.8 age adoption passing confidence
coverage 6.2 -> 6.5.0 age adoption passing confidence
email-validator 1.2.1 -> 1.3.1 age adoption passing confidence
fastjsonschema 2.15.3 -> 2.19.1 age adoption passing confidence
flake8-black ^0.2.3 -> ^0.3.0 age adoption passing confidence
flake8-bugbear (changelog) 22.4.25 -> 22.12.6 age adoption passing confidence
flake8-comprehensions (changelog) 3.7.0 -> 3.14.0 age adoption passing confidence
flake8-isort (changelog) 4.1.1 -> 4.2.0 age adoption passing confidence
isort (source, changelog) 5.10.1 -> 5.13.2 age adoption passing confidence
mkdocs-material (changelog) 8.2.7 -> 8.5.11 age adoption passing confidence
pydantic (changelog) 1.9.1 -> 1.10.15 age adoption passing confidence
pytest (changelog) 7.0.1 -> 7.4.4 age adoption passing confidence
pytest-asyncio (changelog) ^0.16.0 -> ^0.23.0 age adoption passing confidence
pytest-mock (changelog) 3.6.1 -> 3.14.0 age adoption passing confidence

Release Notes

PyCQA/bandit (bandit)

v1.7.8

Compare Source

What's Changed

New Contributors

Full Changelog: PyCQA/bandit@1.7.7...1.7.8

v1.7.7

Compare Source

What's Changed

New Contributors

Full Changelog: PyCQA/bandit@1.7.6...1.7.7

v1.7.6

Compare Source

What's Changed

New Contributors

Full Changelog: PyCQA/bandit@1.7.5...1.7.6

v1.7.5

Compare Source

What's Changed

New Contributors

Full Changelog: PyCQA/bandit@1.7.4...1.7.5

v1.7.4

Compare Source

What's Changed

New Contributors

Full Changelog: PyCQA/bandit@1.7.3...1.7.4

v1.7.3

Compare Source

What's Changed

New Contributors

Full Changelog: PyCQA/bandit@1.7.2...1.7.3

v1.7.2

Compare Source

What's Changed

New Contributors

Full Changelog: PyCQA/bandit@1.7.1...1.7.2

nedbat/coveragepy (coverage)

v6.5.0

Compare Source

  • The JSON report now includes details of which branches were taken, and which
    are missing for each file. Thanks, Christoph Blessing <pull 1438_>. Closes
    issue 1425
    .

  • Starting with coverage.py 6.2, class statements were marked as a branch.
    This wasn't right, and has been reverted, fixing issue 1449_. Note this
    will very slightly reduce your coverage total if you are measuring branch
    coverage.

  • Packaging is now compliant with PEP 517, closing issue 1395.

  • A new debug option --debug=pathmap shows details of the remapping of
    paths that happens during combine due to the [paths] setting.

  • Fix an internal problem with caching of invalid Python parsing. Found by
    OSS-Fuzz, fixing their bug 50381_.

.. _bug 50381: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=50381
.. _PEP 517: https://peps.python.org/pep-0517/
.. _issue 139https://github.com/nedbat/coveragepy/issues/1395395
.. _issue 14https://github.com/nedbat/coveragepy/issues/14251425
.. _issue 1https://github.com/nedbat/coveragepy/issues/1449/1449
.. _pull https://github.com/nedbat/coveragepy/pull/1438l/1438

.. _changes_6-4-4:

v6.4.4

Compare Source

  • Wheels are now provided for Python 3.11.

.. _changes_6-4-3:

v6.4.3

Compare Source

  • Fix a failure when combining data files if the file names contained glob-like
    patterns. Thanks, Michael Krebs and Benjamin Schubert <pull 1405_>_.

  • Fix a messaging failure when combining Windows data files on a different
    drive than the current directory, closing issue 1428. Thanks, Lorenzo Micò <pull 1430_>.

  • Fix path calculations when running in the root directory, as you might do in
    a Docker container. Thanks Arthur Rio <pull 1403_>_.

  • Filtering in the HTML report wouldn't work when reloading the index page.
    This is now fixed. Thanks, Marc Legendre <pull 1413_>_.

  • Fix a problem with Cython code measurement, closing issue 972. Thanks,
    Matus Valo <pull 1347_>
    .

.. _issue 972:https://github.com/nedbat/coveragepy/issues/9722
.. _issue 1428https://github.com/nedbat/coveragepy/issues/142828
.. _pull 134https://github.com/nedbat/coveragepy/pull/1347347
.. _pull 14https://github.com/nedbat/coveragepy/issues/14031403
.. _pull 1https://github.com/nedbat/coveragepy/issues/1405/1405
.. _pull https://github.com/nedbat/coveragepy/issues/1413s/1413
.. _pullhttps://github.com/nedbat/coveragepy/pull/1430ll/1430

.. _changes_6-4-2:

v6.4.2

Compare Source

  • Updated for a small change in Python 3.11.0 beta 4: modules now start with a
    line with line number 0, which is ignored. This line cannot be executed, so
    coverage totals were thrown off. This line is now ignored by coverage.py,
    but this also means that truly empty modules (like __init__.py) have no
    lines in them, rather than one phantom line. Fixes issue 1419_.

  • Internal debugging data added to sys.modules is now an actual module, to
    avoid confusing code that examines everything in sys.modules. Thanks,
    Yilei Yang <pull 1399_>_.

.. _issue 1419:https://github.com/nedbat/coveragepy/issues/14199
.. _pull 1399https://github.com/nedbat/coveragepy/pull/139999

.. _changes_6-4-1:

v6.4.1

Compare Source

  • Greatly improved performance on PyPy, and other environments that need the
    pure Python trace function. Thanks, Carl Friedrich Bolz-Tereick (pull 1381_ and pull 1388). Slightly improved performance when using the C
    trace function, as most environments do. Closes issue 1339
    .

  • The conditions for using tomllib from the standard library have been made
    more precise, so that 3.11 alphas will continue to work. Closes issue 1390_.

.. _issue 1339:https://github.com/nedbat/coveragepy/issues/13399
.. _pull 1381https://github.com/nedbat/coveragepy/pull/138181
.. _pull 138https://github.com/nedbat/coveragepy/pull/1388388
.. _issue 13https://github.com/nedbat/coveragepy/issues/13901390

.. _changes_64:

v6.4

Compare Source

  • Wheels are now provided for Python 3.11.

.. _changes_6-4-3:

v6.3.3

Compare Source

  • Fix: Coverage.py now builds successfully on CPython 3.11 (3.11.0b1) again.
    Closes issue 1367_. Some results for generators may have changed.

.. _issue 1367:https://github.com/nedbat/coveragepy/issues/13677

.. _changes_632:

v6.3.2

Compare Source

  • Fix: adapt to pypy3.9's decorator tracing behavior. It now traces function
    decorators like CPython 3.8: both the @​-line and the def-line are traced.
    Fixes issue 1326_.

  • Debug: added pybehave to the list of :ref:coverage debug <cmd_debug>
    and :ref:`cmd_run_de


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

👻 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

Copy link
Author

mend-for-github-com bot commented Feb 28, 2024

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: poetry.lock
Creating virtualenv aws-lambda-powertools-j4tV00Qc-py3.12 in /home/ubuntu/.cache/pypoetry/virtualenvs
Updating dependencies
Resolving dependencies...


The current project's Python requirement (>=3.6.2,<4.0.0) is not compatible with some of the required packages Python requirement:
  - pytest-asyncio requires Python >=3.8, so it will not be satisfied for Python >=3.6.2,<3.8
  - pytest-asyncio requires Python >=3.8, so it will not be satisfied for Python >=3.6.2,<3.8
  - pytest-asyncio requires Python >=3.8, so it will not be satisfied for Python >=3.6.2,<3.8
  - pytest-asyncio requires Python >=3.8, so it will not be satisfied for Python >=3.6.2,<3.8
  - pytest-asyncio requires Python >=3.8, so it will not be satisfied for Python >=3.6.2,<3.8
  - pytest-asyncio requires Python >=3.8, so it will not be satisfied for Python >=3.6.2,<3.8
  - pytest-asyncio requires Python >=3.8, so it will not be satisfied for Python >=3.6.2,<3.8
  - pytest-asyncio requires Python >=3.8, so it will not be satisfied for Python >=3.6.2,<3.8

Because no versions of pytest-asyncio match >0.23.0,<0.23.1 || >0.23.1,<0.23.2 || >0.23.2,<0.23.3 || >0.23.3,<0.23.4 || >0.23.4,<0.23.5 || >0.23.5,<0.23.5.post1 || >0.23.5.post1,<0.23.6 || >0.23.6,<0.24.0
 and pytest-asyncio (0.23.0) requires Python >=3.8, pytest-asyncio is forbidden.
And because pytest-asyncio (0.23.1) requires Python >=3.8
 and pytest-asyncio (0.23.2) requires Python >=3.8, pytest-asyncio is forbidden.
And because pytest-asyncio (0.23.3) requires Python >=3.8
 and pytest-asyncio (0.23.4) requires Python >=3.8, pytest-asyncio is forbidden.
And because pytest-asyncio (0.23.5) requires Python >=3.8
 and pytest-asyncio (0.23.5.post1) requires Python >=3.8, pytest-asyncio is forbidden.
So, because pytest-asyncio (0.23.6) requires Python >=3.8
 and aws-lambda-powertools depends on pytest-asyncio (^0.23.0), version solving failed.

  • Check your dependencies Python requirement: The Python requirement can be specified via the `python` or `markers` properties
    
    For pytest-asyncio, a possible solution would be to set the `python` property to ">=3.8,<4.0.0"
    For pytest-asyncio, a possible solution would be to set the `python` property to ">=3.8,<4.0.0"
    For pytest-asyncio, a possible solution would be to set the `python` property to ">=3.8,<4.0.0"
    For pytest-asyncio, a possible solution would be to set the `python` property to ">=3.8,<4.0.0"
    For pytest-asyncio, a possible solution would be to set the `python` property to ">=3.8,<4.0.0"
    For pytest-asyncio, a possible solution would be to set the `python` property to ">=3.8,<4.0.0"
    For pytest-asyncio, a possible solution would be to set the `python` property to ">=3.8,<4.0.0"
    For pytest-asyncio, a possible solution would be to set the `python` property to ">=3.8,<4.0.0"

    https://python-poetry.org/docs/dependency-specification/#python-restricted-dependencies,
    https://python-poetry.org/docs/dependency-specification/#using-environment-markers

@mend-for-github-com mend-for-github-com bot changed the title fix(deps): update mend: high confidence minor and patch dependency updates chore(deps): update mend: high confidence minor and patch dependency updates Mar 7, 2024
@mend-for-github-com mend-for-github-com bot changed the title chore(deps): update mend: high confidence minor and patch dependency updates fix(deps): update mend: high confidence minor and patch dependency updates Mar 11, 2024
@mend-for-github-com mend-for-github-com bot changed the title fix(deps): update mend: high confidence minor and patch dependency updates chore(deps): update mend: high confidence minor and patch dependency updates Mar 12, 2024
@mend-for-github-com mend-for-github-com bot changed the title chore(deps): update mend: high confidence minor and patch dependency updates fix(deps): update mend: high confidence minor and patch dependency updates Apr 8, 2024
@mend-for-github-com mend-for-github-com bot changed the title fix(deps): update mend: high confidence minor and patch dependency updates chore(deps): update mend: high confidence minor and patch dependency updates Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants