Skip to content

Update Python dependencies (major) #274

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

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 29, 2025

This PR contains the following updates:

Package Change Age Confidence
cosl 0.0.55 -> 1.0.0 age confidence
ops-scenario ^6.0.3, <6.0.4 -> ^8.0.0, <8.0.1 age confidence
pydantic (changelog) 1.10.17 -> 2.11.7 age confidence

Release Notes

canonical/cos-lib (cosl)

v1.0.0

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.1.1...1.0.0

v0.1.1

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.1.0...0.1.1

v0.1.0

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.57...0.1.0

v0.0.57

Compare Source

Surface an otherwise hard-to-spot issue, where the ingress is handing the coordinated workers an HTTPS endpoint, but the coordinator and workers themselves don't have a certificates relation.

Workers and coordinator now set blocked on TLS misconfiguration.

What's Changed

Full Changelog: canonical/cos-lib@0.0.56...0.0.57

v0.0.56

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.55...0.0.56

pydantic/pydantic (pydantic)

v2.11.7

Compare Source

GitHub release

What's Changed
Fixes

v2.11.6

Compare Source

GitHub release

What's Changed
Fixes

v2.11.5

Compare Source

GitHub release

What's Changed
Fixes

v2.11.4

Compare Source

GitHub release

What's Changed
Packaging
Changes
  • Allow config and bases to be specified together in create_model() by @​Viicos in #​11714.
    This change was backported as it was previously possible (although not meant to be supported)
    to provide model_config as a field, which would make it possible to provide both configuration
    and bases.
Fixes

v2.11.3

Compare Source

GitHub release

What's Changed
Packaging
Fixes

v2.11.2

Compare Source

GitHub release

What's Changed
Fixes

v2.11.1

Compare Source

GitHub release

What's Changed
Fixes
  • Do not override 'definitions-ref' schemas containing serialization schemas or metadata by @​Viicos in #​11644

v2.11.0

Compare Source

GitHub release

What's Changed

Pydantic v2.11 is a version strongly focused on build time performance of Pydantic models (and core schema generation in general).
See the blog post for more details.

Packaging
New Features
Fixes
  • Allow generic typed dictionaries to be used for unpacked variadic keyword parameters by @​Viicos in #​11571
  • Fix runtime error when computing model string representation involving cached properties and self-referenced models by @​Viicos in #​11579
  • Preserve other steps when using the ellipsis in the pipeline API by @​Viicos in #​11626
  • Fix deferred discriminator application logic by @​Viicos in #​11591
New Contributors

v2.10.6

Compare Source

GitHub release

What's Changed
Fixes

v2.10.5

Compare Source

GitHub release

What's Changed
Fixes

v2.10.4

Compare Source

GitHub release

What's Changed
Packaging
Fixes
New Contributors

v2.10.3

Compare Source

GitHub release

What's Changed
Fixes

v2.10.2

Compare Source

GitHub release

What's Changed
Fixes

v2.10.1

Compare Source

GitHub release

What's Changed
Packaging
Fixes
New Contributors

v2.10.0

Compare Source

The code released in v2.10.0 is practically identical to that of v2.10.0b2.

GitHub release

See the v2.10 release blog post for the highlights!

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

v2.9.2

Compare Source

GitHub release

What's Changed
Fixes

v2.9.1

Compare Source

GitHub release

What's Changed
Fixes

v2.9.0

Compare Source

The code released in v2.10.0 is practically identical to that of v2.10.0b2.

GitHub release

See the v2.10 release blog post for the highlights!

What's Changed
Packaging
New Features
Changes
Performance
Fixes

Configuration

📅 Schedule: Branch creation - Between 01:00 AM and 05:59 AM, only on Tuesday ( * 1-5 * * 2 ) in timezone Etc/UTC, 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the not bug or enhancement PR is not 'bug' or 'enhancement'. For release notes label Jul 29, 2025
Copy link
Contributor Author

renovate bot commented Jul 29, 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: poetry.lock
Updating dependencies
Resolving dependencies...

Creating virtualenv non-package-mode-88ziTglk-py3.13 in /home/ubuntu/.cache/pypoetry/virtualenvs

Because no versions of ops-scenario match >8.0.0,<8.0.1
 and ops-scenario (8.0.0) depends on ops (3.0.0), ops-scenario (>=8.0.0,<8.0.1) requires ops (3.0.0).
So, because non-package-mode depends on both ops (>=2.9.0,<2.10) and ops-scenario (^8.0.0, <8.0.1), version solving failed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Libraries: Out of sync not bug or enhancement PR is not 'bug' or 'enhancement'. For release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants