Enforce deprecation DN04: Use charm-entrypoint in charmcraft.yaml parts to define the entry point
Metadata
Current evaluation
DN04 enforcement was implemented and merged, notably in #793 (3b9937a7), which removed the legacy --entrypoint build/pack option.
Resolution: closed resolved
Reason: PR #793, merged as aa51786b, removed --entrypoint from build and pack, directing entry-point declaration through charmcraft.yaml parts. Supporting PRs #767 and #782 added post-build entrypoint validation, directly implementing DN04 despite no recorded closing comment.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | DN04 enforcement was implemented and merged, notably in #793 (3b9937a7), which removed the legacy --entrypoint build/pack option. | |
| stealth/space-bunny-alpha | — | closed stale | DN04 enforcement was closed without a linked PR or commit after years of inactivity. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #793 (commit 3b9937a7) removed the deprecated build/pack --entrypoint option, enforcing DN04 configuration through charmcraft.yaml. | |
| stealth/space-bunny-alpha | — | closed stale | DN04 enforcement was closed without a linked PR or commit and no recorded follow-up for 1,549 days. | |
| stealth/space-bunny-alpha | — | closed stale | DN04 enforcement was closed without a linked PR, commit, version, or maintainer explanation; the only issue body referred to the deprecations documentation. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed as informational. Deprecation DN04 was documented on the official SDK deprecation page without requiring a code change or pull request. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed as informational reference to the official deprecation policy. The issue merely linked to the deprecations page to enforce DN04 and was resolved without discussion or code changes. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Superseded by the DN04 deprecation rollout. The charm-entrypoint requirement in charmcraft.yaml was enforced, closing the tracking issue. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/charmcraft#793
(confidence 95%)
Commit 3b9937a7 removed the legacy command-line entrypoint option as part of DN04 enforcement.
-
Likely Fixed By:
canonical/charmcraft#767
(confidence 85%)
Commit 49c410ca made entrypoint validation apply regardless of its source.
-
Likely Fixed By:
canonical/charmcraft#782
(confidence 82%)
Commits 63643466 and c5f09731 validated entrypoints after building real charms.
-
Related To:
canonical/charmcraft#848
(confidence 80%)
Commit f3176a76 later moved lifecycle-aware entrypoint validation into a proper linter.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #657 Enforce deprecation DN05: Use charm-requirements in charmcraft.yaml parts to define requirements | charmcraft | closed | DN05 was enforced by merged PR #797 (commit 63d57d8c), removing the legacy --requirements option from build and pack. | |
| #654 Enforce deprecation DN02: A charmcraft.yaml configuration file is now required | charmcraft | closed | DN02 was enforced by merged PR #680 (7df649fd), making charmcraft.yaml mandatory for builds and requiring its type key. | |
| #655 Enforce deprecation DN03: Bases configuration is now required | charmcraft | closed | DN03 was enforced by requiring charm bases in configuration; the change was merged in canonical/charmcraft#791 via commit 9c52a73a. |