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): lock file maintenance appengine-backend #2170

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

Conversation

renovate-bot
Copy link
Collaborator

@renovate-bot renovate-bot commented May 7, 2024

Mend Renovate

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
lockFileMaintenance All locks refreshed
Flask-Caching packages minor ==2.1.0 -> ==2.3.0 age adoption passing confidence
grpcio-status packages minor ==1.62.2 -> ==1.63.0 age adoption passing confidence

πŸ”§ This Pull Request updates lock files to use the latest dependency versions.


Configuration

πŸ“… Schedule: Branch creation - "before 6am on wednesday" in timezone Australia/Sydney, 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

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

@forking-renovate forking-renovate bot added the dependencies Pull requests that update a dependency file label May 7, 2024
@renovate-bot renovate-bot changed the title chore(deps): lock file maintenance appengine-backend Lock file maintenance appengine-backend May 13, 2024
Copy link

⚠️ 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: gcp/appengine/Pipfile.lock
Command failed: pipenv lock
Creating a virtualenv for this project...
Pipfile: /tmp/renovate/repos/github/google/osv.dev/gcp/appengine/Pipfile
Using /opt/containerbase/tools/python/3.11.9/bin/python3 (3.11.9) to create virtualenv...
created virtual environment CPython3.11.9.final.0-64 in 2633ms
  creator CPython3Posix(dest=/tmp/renovate/cache/others/virtualenvs/appengine-hhkn4FiX, clear=False, no_vcs_ignore=False, global=False)
  seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle, via=copy, app_data_dir=/home/ubuntu/.local/share/virtualenv)
    added seed packages: pip==24.0, setuptools==69.5.1, wheel==0.43.0
  activators BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator

βœ” Successfully created virtual environment!
Virtualenv location: /tmp/renovate/cache/others/virtualenvs/appengine-hhkn4FiX
Locking [packages] dependencies...

CRITICAL:pipenv.patched.pip._internal.resolution.resolvelib.factory:Cannot install -r /tmp/pipenvd0u_v4l_requirements/pipenv-s1zx9i_s-constraints.txt (line 15), -r /tmp/pipenvd0u_v4l_requirements/pipenv-s1zx9i_s-constraints.txt (line 19), -r /tmp/pipenvd0u_v4l_requirements/pipenv-s1zx9i_s-constraints.txt (line 21) and -r /tmp/pipenvd0u_v4l_requirements/pipenv-s1zx9i_s-constraints.txt (line 6) because these package versions have conflicting dependencies.
[ResolutionFailure]:   File "/opt/containerbase/tools/pipenv/2022.12.19/3.11.9/lib/python3.11/site-packages/pipenv/resolver.py", line 811, in _main
[ResolutionFailure]:       resolve_packages(
[ResolutionFailure]:   File "/opt/containerbase/tools/pipenv/2022.12.19/3.11.9/lib/python3.11/site-packages/pipenv/resolver.py", line 759, in resolve_packages
[ResolutionFailure]:       results, resolver = resolve(
[ResolutionFailure]:       ^^^^^^^^
[ResolutionFailure]:   File "/opt/containerbase/tools/pipenv/2022.12.19/3.11.9/lib/python3.11/site-packages/pipenv/resolver.py", line 738, in resolve
[ResolutionFailure]:       return resolve_deps(
[ResolutionFailure]:       ^^^^^^^^^^^^^
[ResolutionFailure]:   File "/opt/containerbase/tools/pipenv/2022.12.19/3.11.9/lib/python3.11/site-packages/pipenv/utils/resolver.py", line 1100, in resolve_deps
[ResolutionFailure]:       results, hashes, markers_lookup, resolver, skipped = actually_resolve_deps(
[ResolutionFailure]:       ^^^^^^^^^^^^^^^^^^^^^^
[ResolutionFailure]:   File "/opt/containerbase/tools/pipenv/2022.12.19/3.11.9/lib/python3.11/site-packages/pipenv/utils/resolver.py", line 899, in actually_resolve_deps
[ResolutionFailure]:       resolver.resolve()
[ResolutionFailure]:   File "/opt/containerbase/tools/pipenv/2022.12.19/3.11.9/lib/python3.11/site-packages/pipenv/utils/resolver.py", line 687, in resolve
[ResolutionFailure]:       raise ResolutionFailure(message=str(e))
[pipenv.exceptions.ResolutionFailure]: Warning: Your dependencies could not be resolved. You likely have a mismatch in your sub-dependencies.
  You can use $ pipenv install --skip-lock to bypass this mechanism, then run $ pipenv graph to inspect the situation.
  Hint: try $ pipenv lock --pre if it is a pre-release dependency.
ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts


@renovate-bot renovate-bot changed the title Lock file maintenance appengine-backend chore(deps): lock file maintenance appengine-backend May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant