← Back to issue list

Validate the entrypoint after build.

View original Github issue

Metadata

Project
charmcraft
Number
#782
Type
pull request
State
merged
Author
facundobatista
Labels
—
Created
Updated
Closed

Current evaluation

Merged PR #782 fixed the v1.7 packing regression by validating charm entry points after the build lifecycle, allowing build hooks to generate them dynamically.

Resolution: closed resolved

Reason: PR #782 was merged in commit 63643466 with merge commit 5f3b68f1 and explicitly fixed #781. The validation now runs after the build, when generated entry points are available.

Evaluated by: mr-cal-bot

No scores available.

Issue body

Fixes #781.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Merged PR #782 fixed the v1.7 packing regression by validating charm entry points after the build lifecycle, allowing build hooks to generate them dynamically.
stealth/space-bunny-alpha — closed resolved Merged PR #782 (commit 63643466), moving entry-point validation after the build lifecycle so override-build can generate entry points, fixing #781.
stealth/space-bunny-alpha — closed resolved Merged PR #782 via commit 63643466, moving entry point validation after the build lifecycle so dynamically generated charms no longer fail packing in v1.7.
stealth/space-bunny-alpha — closed resolved Merged charmcraft#782 (commit 63643466), deferring entrypoint validation until after the build and fixing premature pack failures in #781.
qwen/qwen3.6-35b-a3b — — Validates the entrypoint after build, resolving issue #781. Merged following single reviewer approval, with two files changed (+149/-108).
qwen3.6-35b-a3b-mtp-q6 — — Merged. The change validates the entrypoint after build, resolving issue #781. Maintainer facundobatista integrated the update without additional comments.

Update history

No update history recorded yet.

Related work

Related issues

Issue Project State Summary Similarity
#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.
77%
#761 The `pack` command does not validate the entrypoint unless it's specified charmcraft closed Fixed in canonical/charmcraft#767 (merge commit 4b64ec0f): pack now validates the default entrypoint when --entrypoint is omitted.
72%
#848 Moved the entrypoint validation (after lifecycle run) to be a proper linter. charmcraft merged Merged PR canonical/charmcraft#848 via c377acc8, moving post-lifecycle entrypoint validation into Charmcraft's linter framework.
71%