chore: upgrade remaining components #439
Conversation
There was a problem hiding this comment.
Pull request overview
Updates the project’s locked dependency set and adjusts the release checklist to reflect the lockfile regeneration command.
Changes:
- Upgraded multiple locked Python dependencies in
uv.lock(runtime + dev/doc tooling). - Updated release checklist instruction to regenerate the lockfile using
uv lock --upgrade.
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| uv.lock | Refreshes the resolved/pinned dependency versions across the project. |
| README.md | Updates the release checklist lockfile generation command. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
README.md
Outdated
| - Dependency track has no critical vulnerabilities [DependencyTrack](https://dep-track.cosmotech.com/projects/b79e84bb-f445-4b32-a56c-5c82c0064aff) | ||
| - Increment the version number (`VERSION`) `/Babylon/version.py` following [semver](https://semver.org/) rules | ||
| - Generate lock file `uv lock` | ||
| - Generate lock file `uv lock --upgrade` |
There was a problem hiding this comment.
The release checklist now uses uv lock --upgrade, which will actively upgrade all dependencies (including transitive ones) at release time. That can introduce unexpected dependency changes during a release cut; consider keeping uv lock for reproducible lock regeneration and documenting uv lock --upgrade as a separate, intentional dependency-bump step (or explicitly noting that releases are expected to upgrade deps).
| - Generate lock file `uv lock --upgrade` | |
| - Generate lock file `uv lock` | |
| - (Optional) To intentionally upgrade dependencies before a release, run `uv lock --upgrade` and commit the updated lock file in a separate dependency-bump change. |
No description provided.