Skip to content

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jan 23, 2025

This PR contains the following updates:

Package Change Age Confidence
molecule (changelog) ==3.4.0 -> ==25.7.0 age confidence

Release Notes

ansible-community/molecule (molecule)

v25.7.0

Compare Source

Enhancements

Bugfixes

Maintenance

v25.6.0

Compare Source

Enhancements

Bugfixes

Maintenance

v25.5.0

Compare Source

Bugfixes

Maintenance

v25.4.0

Compare Source

Enhancements

Bugfixes

v25.3.1

Compare Source

Bugfixes

v25.3.0

Compare Source

Enhancements

Bugfixes

v25.2.0

Compare Source

Major

Enhancements

Bugfixes

v25.1.0

Compare Source

Enhancements

Bugfixes

v24.12.0

Compare Source

Bugfixes

v24.9.0

Compare Source

Enhancements

Bugfixes

v24.8.0

Compare Source

Enhancements

Bugfixes

v24.7.0

Compare Source

Bugfixes

v24.6.1

Compare Source

Bugfixes

v24.6.0

Compare Source

Bugfixes

v24.2.1

Compare Source

Bugfixes

v24.2.0

Compare Source

Major Changes

Minor Changes

Bugfixes

v6.0.3

Compare Source

Bugfixes

v6.0.2

Compare Source

Bugfixes

v6.0.1

Compare Source

Bugfixes

v6.0.0

Compare Source

Major Changes

Minor Changes

Bugfixes

v5.1.0

Compare Source

Minor Changes

Bugfixes

v5.0.1

Compare Source

Bugfixes

v5.0.0

Compare Source

Major Changes

Minor Changes

Bugfixes

Deprecations

v4.0.4

Compare Source

Bugfixes

v4.0.3

Compare Source

Bugfixes

v4.0.2

Compare Source

Bugfixes

v4.0.1

Compare Source

Bugfixes

v4.0.0

Compare Source

Major Changes

Minor Changes

Bugfixes

v3.6.1

Compare Source

Bugfixes

v3.6.0

Compare Source

Minor Changes

Bugfixes

Deprecations

v3.5.2

Compare Source

Bugfixes

Kudos goes to: @​ssbarnea

v3.5.1

Compare Source

Bugfixes

Kudos goes to: @​cjeanner, @​fcharlier and @​ssbarnea

v3.4.1

Compare Source

Bugfixes


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 was generated by Mend Renovate. View the repository job log.

Copy link
Author

renovate bot commented Jan 23, 2025

⚠️ 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: Pipfile.lock
Command failed: pipenv lock
Locking  dependencies...
CRITICAL:pipenv.patched.pip._internal.resolution.resolvelib.factory:Ignored the 
following versions that require a different python version: 24.12.0 
Requires-Python >=3.10; 24.2.0 Requires-Python >=3.10; 24.2.1 Requires-Python 
>=3.10; 24.6.0 Requires-Python >=3.10; 24.6.1 Requires-Python >=3.10; 24.7.0 
Requires-Python >=3.10; 24.8.0 Requires-Python >=3.10; 24.9.0 Requires-Python 
>=3.10; 25.1.0 Requires-Python >=3.10; 25.2.0 Requires-Python >=3.10; 25.3.0 
Requires-Python >=3.10; 25.3.1 Requires-Python >=3.10; 25.4.0 Requires-Python 
>=3.10; 25.5.0 Requires-Python >=3.10; 25.6.0 Requires-Python >=3.10; 
25.6.1.dev7 Requires-Python >=3.10; 25.7.0 Requires-Python >=3.10
CRITICAL:pipenv.patched.pip._internal.resolution.resolvelib.factory:Could not 
find a version that satisfies the requirement molecule==25.7.0 (from versions: 
1.20.1, 1.20.3, 1.21.1, 1.22.0, 1.23.0, 1.25.0, 1.25.1, 2.10.0, 2.10.1, 2.11.0, 
2.12.0, 2.12.1, 2.13.0, 2.13.1, 2.14.0, 2.15.0, 2.16.0, 2.17.0, 2.18.0, 2.18.1, 
2.19.0, 2.20.0.0a1, 2.20.0.0a2, 2.20.0, 2.20.1, 2.20.2, 2.22rc1, 2.22rc3, 
2.22rc6, 2.22, 3.0a0, 3.0a1, 3.0a2, 3.0a3, 3.0a4, 3.0a5, 3.0a6, 3.0a8, 3.0a9, 
3.0.0, 3.0.1, 3.0.2, 3.0.2.1, 3.0.3, 3.0.4, 3.0.5, 3.0.6, 3.0.7, 3.0.8, 3.1.0a1,
3.1.0a2, 3.1.0, 3.1.1, 3.1.2, 3.1.3, 3.1.4, 3.1.5, 3.2.0a0, 3.2.0a1, 3.2.0a2, 
3.2.0, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.3.0, 3.3.1, 3.3.2, 3.3.3, 3.3.4, 3.4.0, 
3.4.1, 3.5.0a0, 3.5.1, 3.5.2, 3.6.0, 3.6.1, 4.0.0a0, 4.0.0, 4.0.1, 4.0.2, 4.0.3,
4.0.4, 5.0.0a0, 5.0.0a1, 5.0.0, 5.0.1, 5.1.0, 6.0.0a0, 6.0.0a1, 6.0.0a2, 
6.0.0b0, 6.0.0rc0, 6.0.0, 6.0.1, 6.0.2, 6.0.3)
[ResolutionFailure]:   File 
"/opt/containerbase/tools/pipenv/2025.0.4/3.9.23/lib/python3.9/site-packages/pip
env/resolver.py", line 451, in main
[ResolutionFailure]:       _main(
[ResolutionFailure]:   File 
"/opt/containerbase/tools/pipenv/2025.0.4/3.9.23/lib/python3.9/site-packages/pip
env/resolver.py", line 436, in _main
[ResolutionFailure]:       resolve_packages(
[ResolutionFailure]:   File 
"/opt/containerbase/tools/pipenv/2025.0.4/3.9.23/lib/python3.9/site-packages/pip
env/resolver.py", line 400, in resolve_packages
[ResolutionFailure]:       results, resolver = resolve_deps(
[ResolutionFailure]:   File 
"/opt/containerbase/tools/pipenv/2025.0.4/3.9.23/lib/python3.9/site-packages/pip
env/utils/resolver.py", line 1083, in resolve_deps
[ResolutionFailure]:       results, hashes, internal_resolver = 
actually_resolve_deps(
[ResolutionFailure]:   File 
"/opt/containerbase/tools/pipenv/2025.0.4/3.9.23/lib/python3.9/site-packages/pip
env/utils/resolver.py", line 811, in actually_resolve_deps
[ResolutionFailure]:       resolver.resolve()
[ResolutionFailure]:   File 
"/opt/containerbase/tools/pipenv/2025.0.4/3.9.23/lib/python3.9/site-packages/pip
env/utils/resolver.py", line 471, in resolve
[ResolutionFailure]:       raise ResolutionFailure(message=e)
Your dependencies could not be resolved. You likely have a mismatch in your 
sub-dependencies.
You can use $ pipenv run pip install <requirement_name> to bypass this 
mechanism, then run $ pipenv graph to inspect the versions actually installed in
the virtualenv.
Hint: try $ pipenv lock --pre if it is a pre-release dependency.
ERROR: No matching distribution found for molecule==25.7.0

Your dependencies could not be resolved. You likely have a mismatch in your 
sub-dependencies.
You can use $ pipenv run pip install <requirement_name> to bypass this 
mechanism, then run $ pipenv graph to inspect the versions actually installed in
the virtualenv.
Hint: try $ pipenv lock --pre if it is a pre-release dependency.
ERROR: Failed to lock Pipfile.lock!

@renovate renovate bot force-pushed the renovate/molecule-25.x branch from 3129558 to d66ecbc Compare January 28, 2025 13:01
@renovate renovate bot force-pushed the renovate/molecule-25.x branch 2 times, most recently from 0a4c627 to 8ccda57 Compare February 19, 2025 19:48
@renovate renovate bot force-pushed the renovate/molecule-25.x branch from 8ccda57 to ab21dbf Compare April 1, 2025 19:32
@renovate renovate bot force-pushed the renovate/molecule-25.x branch from ab21dbf to 37f9d44 Compare May 26, 2025 09:56
@renovate renovate bot force-pushed the renovate/molecule-25.x branch from 37f9d44 to e69c64c Compare June 18, 2025 13:14
@renovate renovate bot force-pushed the renovate/molecule-25.x branch from e69c64c to 2d011f5 Compare July 30, 2025 00:29
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.

0 participants