mailersend-python icon indicating copy to clipboard operation
mailersend-python copied to clipboard

chore(deps): update dependency pre-commit to v3

Open renovate[bot] opened this issue 2 years ago • 1 comments

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
pre-commit ^2.12.1 -> ^3.0.0 age adoption passing confidence

Release Notes

pre-commit/pre-commit (pre-commit)

v3.6.2

Compare Source

==================

Fixes

v3.6.1

Compare Source

==================

Fixes

v3.6.0

Compare Source

==================

Features
Fixes
Updating

v3.5.0

Compare Source

==================

Features
Fixes
Migrating

v3.4.0

Compare Source

==================

Features
Fixes

v3.3.3

Compare Source

==================

Fixes

v3.3.2

Compare Source

==================

Fixes

v3.3.1

Compare Source

==================

Fixes

v3.3.0

Compare Source

==================

Features

v3.2.2

Compare Source

==================

Fixes

v3.2.1

Compare Source

==================

Fixes

v3.2.0

Compare Source

==================

Features
Fixes

v3.1.1

Compare Source

==================

Fixes

v3.1.0

Compare Source

==================

Fixes
Updating

v3.0.4

Compare Source

==================

Fixes

v3.0.3

Compare Source

==================

Fixes

v3.0.2

Compare Source

==================

Fixes

v3.0.1

Compare Source

==================

Fixes

v3.0.0

Compare Source

==================

Features
Fixes
Updating
  • Drop support for python<3.8
  • Drop support for top-level list, use pre-commit migrate-config to update.
  • Drop support for sha to specify revision, use pre-commit migrate-config to update.
  • Remove pre-commit-validate-config and pre-commit-validate-manifest, use pre-commit validate-config and pre-commit validate-manifest instead.
  • language: golang hooks must use go.mod to specify dependencies

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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • [ ] 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[bot] avatar Sep 12 '23 15:09 renovate[bot]

⚠ 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
installing v2 tool python v3.11.5
[15:29:59.861] INFO (9): Installing tool python v3.11.5...
linking tool python v3.11.5
Python 3.11.5
pip 23.2.1 from /opt/containerbase/tools/python/3.11.5/lib/python3.11/site-packages/pip (python 3.11)
[15:30:06.630] INFO (9): Installed tool python in 6.7s.
[15:30:07.118] INFO (170): Installing tool poetry v1.2.2...
installing v2 tool poetry v1.2.2
linking tool poetry v1.2.2
Poetry (version 1.2.2)
[15:30:16.467] INFO (170): Installed tool poetry in 9.3s.
Creating virtualenv mailersend-GAMjx6dx-py3.11 in /home/ubuntu/.cache/pypoetry/virtualenvs
Updating dependencies
Resolving dependencies...


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

Because no versions of pre-commit match >3.0.0,<3.0.1 || >3.0.1,<3.0.2 || >3.0.2,<3.0.3 || >3.0.3,<3.0.4 || >3.0.4,<3.1.0 || >3.1.0,<3.1.1 || >3.1.1,<3.2.0 || >3.2.0,<3.2.1 || >3.2.1,<3.2.2 || >3.2.2,<3.3.0 || >3.3.0,<3.3.1 || >3.3.1,<3.3.2 || >3.3.2,<3.3.3 || >3.3.3,<3.4.0 || >3.4.0,<4.0.0
 and pre-commit (3.0.0) requires Python >=3.8, pre-commit is forbidden.
And because pre-commit (3.0.1) requires Python >=3.8, pre-commit is forbidden.
And because pre-commit (3.0.2) requires Python >=3.8
 and pre-commit (3.0.3) requires Python >=3.8, pre-commit is forbidden.
And because pre-commit (3.0.4) requires Python >=3.8
 and pre-commit (3.1.0) requires Python >=3.8, pre-commit is forbidden.
And because pre-commit (3.1.1) requires Python >=3.8
 and pre-commit (3.2.0) requires Python >=3.8, pre-commit is forbidden.
And because pre-commit (3.2.1) requires Python >=3.8
 and pre-commit (3.2.2) requires Python >=3.8, pre-commit is forbidden.
And because pre-commit (3.3.0) requires Python >=3.8
 and pre-commit (3.3.1) requires Python >=3.8, pre-commit is forbidden.
And because pre-commit (3.3.2) requires Python >=3.8
 and pre-commit (3.3.3) requires Python >=3.8, pre-commit is forbidden.
So, because pre-commit (3.4.0) requires Python >=3.8
 and mailersend depends on pre-commit (^3.0.0), version solving failed.

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

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

renovate[bot] avatar Sep 12 '23 15:09 renovate[bot]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 3.x releases. But if you manually upgrade to 3.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

renovate[bot] avatar May 30 '24 14:05 renovate[bot]