providers: set lxd project to 'charmcraft'
Metadata
Current evaluation
Merged a fix setting the LXD project to 'charmcraft' instead of 'default', resolving a regression from the craft-providers migration. Approved by one reviewer, the change updates two files with a +10/-4 diff.
Suggested action: —
No scores available.
Issue body
Set the project to `charmcraft` instead of the default project `default`.
This fixes a regression from migrating to the new craft-providers interface.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Merged a fix setting the LXD project to 'charmcraft' instead of 'default', resolving a regression from the craft-providers migration. Approved by one reviewer, the change updates two files with a +10/-4 diff. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged. Updates the LXD project setting from 'default' to 'charmcraft', fixing a regression caused by the migration to the new craft-providers interface. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged a fix that sets the LXD project to 'charmcraft' instead of 'default', resolving a regression from the craft-providers interface migration. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #3660 providers: integrate craft-providers support | snapcraft | merged | Integrated craft-providers support to run lifecycle commands in LXD or Multipass build providers. Merged with 1338 additions and 41 deletions across 22 files, adapting Charmcraft's implementation after reviewer approval. | |
| #110 providers: move lxd project name out of craft-providers interface | rockcraft | merged | Merged refactoring that moves rockcraft's project name from lxd.py to providers.py in the craft-providers interface. Approved by one reviewer, passed CI, and successfully integrated. | |
| #1640 Incompatibility with latest LXD LTS | charmcraft | closed | charmcraft failed parsing LXD 5.21 LTS version strings due to the appended LTS suffix. The issue was resolved by upgrading craft-providers to 1.23.1 and releasing the fix in charmcraft 2.6.0, now available on stable. | |
| #474 charmcraft: perform LXD checks before use (CRAFT-420) | charmcraft | merged | Merged to charmcraft, adding pre-use LXD readiness and permission validation to the provider module. Consolidates existing checks, updates mocks, and improves import structure. Approved by two reviewers and passed CI. | |
| #9 providers: add build provider support (CRAFT-28) | rockcraft | merged | Merged integration of rockcraft with craft-providers to run build providers on LXD instances. The change ports Charmcraft glue code, hardwires execution to LXD, and defers user messages and log retrieval to follow-up PRs. Approved and passed CI. | |
| #403 build(deps): bump craft-providers to 1.19.2 | rockcraft | merged | Merged bumping craft-providers to 1.19.2. Fixes LXD startup failures from base tag changes and enforces disk device requirements in the default LXD profile. Approved by two reviewers with passing CI. | |
| #1370 build(deps): bump craft-providers to 1.19.2 | charmcraft | merged | Merged after three approvals and passing CI. Bumps craft-providers to 1.19.2, fixing LXD instance startup failures by updating the base compatibility tag from base-v2 to base-v3 and requiring a disk device in the default LXD profile. | |
| #509 build(deps): bump craft-providers to 1.23.1 | rockcraft | merged | Merged dependency update bumping craft-providers to 1.23.1. Resolves LTS LXD version parsing. Approved by two reviewers, passed CI, and modified three files. | |
| #4437 build(deps): bump craft-providers to 1.19.2 | snapcraft | merged | Merged update bumping craft-providers to 1.19.2. Resolves LXD instance startup failures by updating the base compatibility tag from base-v2 to base-v3. Approved by reviewers and passed CI. | |
| #137 build(deps): bump craft-providers to 1.19.2 | craft-application | merged | Merged dependency update to craft-providers 1.19.2. Resolves LXD instance startup failures by migrating the base compatibility tag from v2 to v3. Approved by reviewers, passed CI, and merged with no coverage impact. |