Update dependency setuptools to v70 [SECURITY]

renovate[bot] commented 2 months ago

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
setuptools (changelog)	`~=68.0.0` -> `~=70.0.0`
setuptools (changelog)	`==65.5.1` -> `==70.0.0`

GitHub Vulnerability Alerts

CVE-2024-6345

A vulnerability in the package_index module of pypa/setuptools versions up to 69.1.1 allows for remote code execution via its download functions. These functions, which are used to download packages from URLs provided by users or retrieved from package index servers, are susceptible to code injection. If these functions are exposed to user-controlled inputs, such as package URLs, they can execute arbitrary commands on the system. The issue is fixed in version 70.0.

Release Notes

pypa/setuptools (setuptools)

### [`v70.0.0`](https://togithub.com/pypa/setuptools/compare/v69.5.1...v70.0.0) [Compare Source](https://togithub.com/pypa/setuptools/compare/v69.5.1...v70.0.0) ### [`v69.5.1`](https://togithub.com/pypa/setuptools/compare/v69.5.0...v69.5.1) [Compare Source](https://togithub.com/pypa/setuptools/compare/v69.5.0...v69.5.1) ### [`v69.5.0`](https://togithub.com/pypa/setuptools/compare/v69.4.2...v69.5.0) [Compare Source](https://togithub.com/pypa/setuptools/compare/v69.4.2...v69.5.0) ### [`v69.4.2`](https://togithub.com/pypa/setuptools/compare/v69.4.1...v69.4.2) [Compare Source](https://togithub.com/pypa/setuptools/compare/v69.4.1...v69.4.2) ### [`v69.4.1`](https://togithub.com/pypa/setuptools/compare/v69.4.0...v69.4.1) [Compare Source](https://togithub.com/pypa/setuptools/compare/v69.4.0...v69.4.1) ### [`v69.4.0`](https://togithub.com/pypa/setuptools/compare/v69.3.1...v69.4.0) [Compare Source](https://togithub.com/pypa/setuptools/compare/v69.3.1...v69.4.0) ### [`v69.3.1`](https://togithub.com/pypa/setuptools/compare/v69.3.0...v69.3.1) [Compare Source](https://togithub.com/pypa/setuptools/compare/v69.3.0...v69.3.1) ### [`v69.3.0`](https://togithub.com/pypa/setuptools/compare/v69.2.0...v69.3.0) [Compare Source](https://togithub.com/pypa/setuptools/compare/v69.2.0...v69.3.0) ### [`v69.2.0`](https://togithub.com/pypa/setuptools/compare/v69.1.1...v69.2.0) [Compare Source](https://togithub.com/pypa/setuptools/compare/v69.1.1...v69.2.0) ### [`v69.1.1`](https://togithub.com/pypa/setuptools/compare/v69.1.0...v69.1.1) [Compare Source](https://togithub.com/pypa/setuptools/compare/v69.1.0...v69.1.1) ### [`v69.1.0`](https://togithub.com/pypa/setuptools/compare/v69.0.3...v69.1.0) [Compare Source](https://togithub.com/pypa/setuptools/compare/v69.0.3...v69.1.0) ### [`v69.0.3`](https://togithub.com/pypa/setuptools/compare/v69.0.2...v69.0.3) [Compare Source](https://togithub.com/pypa/setuptools/compare/v69.0.2...v69.0.3) ### [`v69.0.2`](https://togithub.com/pypa/setuptools/compare/v69.0.1...v69.0.2) [Compare Source](https://togithub.com/pypa/setuptools/compare/v69.0.1...v69.0.2) ### [`v69.0.1`](https://togithub.com/pypa/setuptools/compare/v69.0.0...v69.0.1) [Compare Source](https://togithub.com/pypa/setuptools/compare/v69.0.0...v69.0.1) ### [`v69.0.0`](https://togithub.com/pypa/setuptools/compare/v68.2.2...v69.0.0) [Compare Source](https://togithub.com/pypa/setuptools/compare/v68.2.2...v69.0.0) ### [`v68.2.2`](https://togithub.com/pypa/setuptools/compare/v68.2.1...v68.2.2) [Compare Source](https://togithub.com/pypa/setuptools/compare/v68.2.1...v68.2.2) ### [`v68.2.1`](https://togithub.com/pypa/setuptools/compare/v68.2.0...v68.2.1) [Compare Source](https://togithub.com/pypa/setuptools/compare/v68.2.0...v68.2.1) ### [`v68.2.0`](https://togithub.com/pypa/setuptools/compare/v68.1.2...v68.2.0) [Compare Source](https://togithub.com/pypa/setuptools/compare/v68.1.2...v68.2.0) ### [`v68.1.2`](https://togithub.com/pypa/setuptools/compare/v68.1.0...v68.1.2) [Compare Source](https://togithub.com/pypa/setuptools/compare/v68.1.0...v68.1.2) ### [`v68.1.0`](https://togithub.com/pypa/setuptools/compare/v68.0.0...v68.1.0) [Compare Source](https://togithub.com/pypa/setuptools/compare/v68.0.0...v68.1.0)

Configuration

📅 Schedule: Branch creation - "" in timezone Europe/Paris, 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 these updates again.

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

This PR was generated by Mend Renovate. View the repository job log.

sonarcloud[bot] commented 1 month ago

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

renovate[bot] commented 1 month ago

⚠️ 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

Updating dependencies
Resolving dependencies...

Warning: In a future version of Poetry, PyPI will be disabled automatically if at least one custom source is configured with another priority than 'explicit'. In order to avoid a breaking change and make your pyproject.toml forward compatible, add PyPI explicitly via 'poetry source add pypi'. By the way, this has the advantage that you can set the priority of PyPI as with any other source.

Because ansible-playbook-grapher (1.2.0) depends on ansible-core (>=2.11,<2.13)
 and no versions of ansible-playbook-grapher match >1.2.0,<1.3.0, ansible-playbook-grapher (>=1.2.0,<1.3.0) requires ansible-core (>=2.11,<2.13).
So, because nabla-hooks depends on both ansible-core (~=2.15.2) and ansible-playbook-grapher (~=1.2.0), version solving failed.

renovate[bot] commented 1 month ago

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 70.x releases. But if you manually upgrade to 70.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.

AlbanAndrieu / nabla-hooks