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

Update dependency pydantic to v2.8.2 #127

Merged
merged 2 commits into from
Jul 17, 2024
Merged

Update dependency pydantic to v2.8.2 #127

merged 2 commits into from
Jul 17, 2024

Conversation

RKIMetadataExchange
Copy link
Contributor

This PR contains the following updates:

Package Type Update Change
pydantic (changelog) project.dependencies minor ==2.7.4 -> ==2.8.2

Release Notes

pydantic/pydantic (pydantic)

v2.8.2

Compare Source

GitHub release

What's Changed
Fixes

v2.8.1

Compare Source

GitHub release

What's Changed
Packaging
Fixes

v2.8.0

Compare Source

GitHub release

The code released in v2.8.0 is functionally identical to that of v2.8.0b1.

What's Changed
Packaging
New Features
Changes
Performance
Internal Improvements
Fixes
New Contributors

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 Renovate Bot.

@RKIMetadataExchange
Copy link
Contributor Author

⚠️ 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: pdm.lock
Command failed: pdm update --no-sync --update-eager pydantic
WARNING: Project requires a python version of <3.13,>=3.11, The virtualenv is being created for you as it cannot be matched to the right version.
INFO: python.use_venv is on, creating a virtualenv for this project...
Virtualenv is created successfully at /tmp/renovate/repos/github/robert-koch-institut/mex-extractors/.venv
STATUS: Resolving dependencies
STATUS: Resolving: new pin python<3.13,>=3.11
STATUS: Resolving: new pin pydantic 2.8.2
STATUS: Resolving: new pin pydantic-core 2.20.1
STATUS: Resolving: new pin typing-extensions 4.12.2
STATUS: Resolving: new pin annotated-types 0.7.0
🔒 Lock failed
ERROR: Unable to find a resolution for pydantic
because of the following conflicts:
  pydantic==2.7.4 (from mex-common@git+https://github.com/robert-koch-institut/[email protected])
  pydantic==2.7.4 (from mex-common@git+https://github.com/robert-koch-institut/mex-common.git@f53fefaa79e84a1198eeb0e0a8a90a27c0ea9382)
  pydantic==2.8.2 (from project)
To fix this, you could loosen the dependency version constraints in pyproject.toml. See https://pdm-project.org/en/latest/usage/lockfile/#solve-the-locking-failure for more details.
See /home/ubuntu/.local/state/pdm/log/pdm-lock-1hv7hdvp.log for detailed debug log.
[ResolutionImpossible]: Unable to find a resolution
WARNING: Add '-v' to see the detailed traceback

@RKIMetadataExchange RKIMetadataExchange self-assigned this Jul 11, 2024
@erichesse erichesse merged commit faa345e into main Jul 17, 2024
7 checks passed
@erichesse erichesse deleted the renovate/pydantic-2.x branch July 17, 2024 11:45
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.

2 participants