Remove uv.lock from `kubernetes` and `machine` profiles
Metadata
Current evaluation
Closed as fixed by merged PR canonical/charmcraft#2754 (commit 0be5a5e7): kubernetes/machine profiles no longer ship uv.lock, dependencies are bounded, and init output now tells developers to run 'uv lock'.
Resolution: closed resolved
Reason: PR #2754 ("feat(profiles): bound dependencies, remove uv.lock files, improve init output") was merged as commit 0be5a5e7 and explicitly fixes #2749. It removed the bundled uv.lock templates from the kubernetes and machine profiles and updated the post-init output to instruct developers to run 'uv lock'.
Evaluated by: mr-cal-bot
No scores available.
Issue body
At the Madrid sprints in May, we decided to stop shipping `uv.lock` when initing charms with `--profile kubernetes` and `--profile machine`. It's awkward to keep the locked versions of packages up-to-date. Instead, we expect the charm developer to run `uv lock` after initing their charm.
I also propose a clean-up of the `init` output. Something like:
```
Created project files for your charm:
charmcraft.yaml
pyproject.toml
README.md
src/charm.py
src/demo_app.py
...
To manage your charm's dependencies, use uv.
To migrate from the Charm plugin to the uv plugin, see:
https://documentation.ubuntu.com/charmcraft/stable/howto/migrate-plugins/charm-to-uv/
Next steps:
1. Run 'uv lock'
2. Edit charmcraft.yaml and pyproject.toml to provide metadata, then commit (including uv.lock)
3. Write your charm code and tests
```
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Closed as fixed by merged PR canonical/charmcraft#2754 (commit 0be5a5e7): kubernetes/machine profiles no longer ship uv.lock, dependencies are bounded, and init output now tells developers to run 'uv lock'. | |
| stealth/space-bunny-alpha | — | closed resolved | Implemented as PR canonical/charmcraft#2754 (commit 0be5a5e7): `init` no longer writes uv.lock for kubernetes/machine profiles and now tells developers to run 'uv lock' as next step. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed by merged PR canonical/charmcraft#2754 (commit 0be5a5e7): kubernetes and machine profiles no longer ship uv.lock, and init now prompts developers to run uv lock. | |
| qwen/qwen3.6-35b-a3b | — | — | Merged changes to remove uv.lock from kubernetes and machine profiles during charm initialization. Updated init output to guide developers in running uv lock manually. | |
| qwen/qwen3.6-35b-a3b | — | — | Merged the removal of uv.lock from kubernetes and machine profiles. The init command now omits the lock file and displays updated guidance for developers to run uv lock manually. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed. Resolved via a pull request that removes uv.lock from kubernetes and machine profiles and updates the init command output to guide developers in running uv lock manually. | |
| qwen/qwen3.6-35b-a3b | — | — | Implemented via a merged pull request. uv.lock is no longer generated for kubernetes and machine profiles during initialization. Developers must now run uv lock manually, and init output was updated accordingly. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
5
Complexity:
20
Confidence:
90
Support Request:
0
|
keep open | Proposal to remove `uv.lock` from `kubernetes` and `machine` profiles and update `init` output; author plans to open a PR. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
5
Complexity:
15
Confidence:
90
Support Request:
0
|
needs triage | Contributor proposes removing uv.lock from kubernetes and machine profiles during charm init, updating init output messages, and plans to open a PR. |
Update history
| Date | Change |
|---|---|
| closed |
Related work
-
Likely Fixed By:
canonical/charmcraft#2754
(confidence 97%)
Merged PR referencing fixes #2749, commit 0be5a5e7; removed uv.lock from kubernetes/machine init templates and rewrote init instructions
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2754 feat(profiles): bound dependencies, remove uv.lock files, improve init output | charmcraft | merged | Merged PR #2754 (0be5a5e7), bounding Kubernetes/machine dependencies, removing bundled uv.lock files, and improving init output and docs; fixes #2749. |