Charmcraft's entry point option should be in charmcraft.yaml
Metadata
Current evaluation
Fixed in canonical/charmcraft#468 (merged as d892b3f3): charmcraft.yaml gained charm-plugin entrypoint and requirements properties for reproducible, zero-config charmcraft pack builds.
Resolution: closed resolved
Reason: Merged PR #468 resolved the issue in commit d892b3f3 by adding the charm plugin's entrypoint and requirements properties to charmcraft.yaml and deprecating equivalent CLI options. Follow-up PR #472 fixed related requirements and virtualenv behavior.
Evaluated by: mr-cal-bot
No scores available.
Issue body
Two reasons:
- Reproduceable results by just running `charmcraft pack`
- Zero configuration CI with the expected outcome by just running `charmcraft pack`
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Fixed in canonical/charmcraft#468 (merged as d892b3f3): charmcraft.yaml gained charm-plugin entrypoint and requirements properties for reproducible, zero-config charmcraft pack builds. | |
| stealth/space-bunny-alpha | — | closed resolved | Entrypoint moved into charmcraft.yaml as a charm plugin property. Fixed by canonical/charmcraft#468, merged as commit d892b3f3, adding charm-plugin entrypoint and requirements properties (CRAFT-393). | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed in canonical/charmcraft#468, merged as d892b3f3: charmcraft.yaml now supports charm-plugin entrypoint and requirements properties for reproducible, zero-config charmcraft pack builds. | |
| stealth/space-bunny-alpha | — | closed resolved | Added entrypoint and requirements settings to the charm plugin in merged PR #468 (commit dac3d2d8), enabling declarative configuration through charmcraft.yaml. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Charmcraft's entry point option was moved to charmcraft.yaml to enable reproducible builds and zero-configuration CI. Resolved and merged in pull request #468. | |
| qwen/qwen3.6-35b-a3b | — | — | Charmcraft's entry point option was moved to charmcraft.yaml to enable reproducible builds and zero-configuration CI. The request was resolved and implemented in pull request #468. | |
| qwen/qwen3.6-35b-a3b | — | — | The entry point configuration was moved to charmcraft.yaml to enable reproducible builds and zero-configuration CI. Resolved and merged in pull request #468. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Charmcraft entry point configuration was moved to charmcraft.yaml to enable reproducible builds and zero-config CI. The request was fixed and merged in pull request #468. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/charmcraft#468
(confidence 100%)
Merged PR implementing charmcraft.yaml entrypoint and requirements properties.
-
Related To:
canonical/charmcraft#472
(confidence 95%)
Follow-up merged fix for priming the virtualenv when requirements are configured.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #468 parts: add entrypoint and requirements properties to charm plugin (CRAFT-393) | charmcraft | merged | Merged as d892b3f3, adding entrypoint and requirements plugin properties, deprecating equivalent CLI flags, and rejecting dual configuration. A regression was later fixed in #472. | |
| #1149 command: charmcraft init to use charmcraft.yaml only | charmcraft | merged | Merged in ca4df024: charmcraft init now generates a unified charmcraft.yaml containing metadata, actions, and config, with profile descriptions and an updated URL. | |
| #781 v1.7 regression: `pack` errors out prematurely with `Charm entry point was not found` | charmcraft | closed | Fixed by merged PR canonical/charmcraft#782 (commit 63643466), moving entry-point validation after the build lifecycle so override-build can generate custom entry points. |