Update to pydantic-yaml >=1.0.0
Metadata
Current evaluation
The pydantic-yaml 1.x migration was bypassed when PR #811 removed the unnecessary dependency in commit 1debce16, after PR #498 had temporarily frozen it below 1.0.
Resolution: closed superseded
Reason: PR #811, commit 1debce16, removed pydantic-yaml entirely, making the planned >=1.0 refactor obsolete. PR #498 had previously frozen the dependency below 1.0 pending this work.
Evaluated by: mr-cal-bot
No scores available.
Issue body
### What needs to get done
Update dependencies to pydantic-yaml >= 1.0.0 and do the code changes that come with it.
### Why it needs to get done
Version 1.0 has some API changes that rearrange things, so we'll need to do some slight refactoring.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed superseded | The pydantic-yaml 1.x migration was bypassed when PR #811 removed the unnecessary dependency in commit 1debce16, after PR #498 had temporarily frozen it below 1.0. | |
| stealth/space-bunny-alpha | — | closed stale | The pydantic-yaml 1.x migration was not delivered: PR #1191 was closed unmerged, leaving the planned refactor outstanding. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without documented resolution. The pydantic-yaml update request was synced to internal Jira ticket CRAFT-2940, but no code changes or merge details were provided. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
20
Confidence:
75
Support Request:
5
|
close stale | Unlabelled dependency update request for pydantic-yaml >=1.0.0. Inactive for over a year with only an automated Jira migration comment. No maintainer assessment or assignee. |
Update history
| Date | Change |
|---|---|
| closed |
Related work
-
Superseded By:
craft-parts#811
(confidence 98%)
Commit 1debce16 removed pydantic-yaml as unnecessary.
-
Related To:
craft-parts#498
(confidence 96%)
PR #498 capped pydantic-yaml below 1.0 pending the migration tracked by #499.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1194 Update to pydantic-yaml >= 1.0 | charmcraft | closed | pydantic-yaml 1.x integration was completed in commit 22c1a49f during Charmcraft's Pydantic 2 migration, after PR #1191 was closed unmerged. | |
| #49 deps: freeze pydantic-yaml < 1.0 | craft-application | merged | Merged PR #49 as commit 97c620ab, capping pydantic-yaml below 1.0 to avoid potentially breaking dependency releases. | |
| #498 deps: freeze pydantic-yaml <1.0.0 | craft-parts | merged | Merged PR #498 as 5b463227, capping pydantic-yaml below 1.0.0 to avoid breaking API changes pending the refactor tracked in #499. | |
| #519 deps: freeze pydantic-yaml <1.0.0 (#498) | craft-parts | merged | Merged PR #519 as cf61a4f6, cherry-picking 5b463227 from #498 to cap pydantic-yaml below 1.0.0 and avoid breaking API changes pending refactoring. | |
| #1191 chore(deps): update dependency pydantic-yaml to v1 | charmcraft | closed | pydantic-yaml 1.1.0 was not merged; PR #1191 was closed on 2023-07-26 because manual integration was required, and Renovate then ignored future 1.x updates. | |
| #164 chore(deps): update dependency pydantic-yaml to v1 | craft-application | closed | pydantic-yaml 1.x update PR #164 was closed unmerged; Renovate marked the update as ignored. | |
| #971 chore(deps): update dependency pydantic-yaml to v0.9.0 | charmcraft | closed | The pydantic-yaml 0.9.0 bump was closed unmerged after receiving no reviews or CI; a later 1.x migration completed in commit 22c1a49f via #1194. | |
| #645 chore(deps): update dependency pydantic-yaml to v1 | craft-parts | closed | Closed unmerged after 974 days; the dependency remained below v1 and was later removed by merged PR #811 (commit 1debce16). | |
| #841 Incorrect extra set on pydantic-yaml | craft-parts | closed | Fixed by merged PR #811 (commit 1debce16), which removed the unnecessary pydantic-yaml dependency and its nonexistent pyyaml extra. | |
| #159 setup: pin pydantic-yaml and pydantic versions (CRAFT-718) | craft-parts | merged | Merged in #159 via 0226365f, pinning pydantic-yaml 0.4.2 and pydantic 1.9.0 to restore compatibility and fix #158. |