charmcraft V1.5.0 and V1.6.0 not bundling up bash actions
Metadata
Current evaluation
Reported that charmcraft 1.5.0/1.6.0 omitted the charm's `actions` directory from built charms. Maintainer facundobatista closed it as a duplicate of #764, which was fixed by merged PR #768 (commit 5ada563c).
Resolution: closed superseded
Reason: facundobatista closed the report on 2022-05-10 as a duplicate, with the work tracked in issue #764 ("The `actions` directory is not being included by default"). That issue was resolved by merged PR #768, commit 5ada563c, which makes charmcraft include an existing root `actions` directory in the built charm.
Evaluated by: mr-cal-bot
No scores available.
Issue body
I'd been attempting to get Juju team to look into an issue with charmhub, they've sinced said to file a bug against charmcraft
https://bugs.launchpad.net/juju/+bug/1971495/comments/6
"The packaged charm uploaded to charmhub seems to be missing the actions directory.
I packaged a test charm and saw that the actions directory was not included in the charm."
I am currently able to work around this issue by wiring in my charms directly.. please let me know how I can help debug this
Edit : Link to the discourse discussion as well https://discourse.charmhub.io/t/juju-action-only-works-with-local-charm-not-with-charmhub-copy/6022/10?u=emcp
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed superseded | Reported that charmcraft 1.5.0/1.6.0 omitted the charm's `actions` directory from built charms. Maintainer facundobatista closed it as a duplicate of #764, which was fixed by merged PR #768 (commit 5ada563c). | |
| stealth/space-bunny-alpha | — | closed superseded | Closed as a duplicate of charmcraft#764, where maintainers tracked omission of the default actions directory; no separate fix was cited for #763. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed as a duplicate. The charmcraft packaging bug omitting the bash actions directory was confirmed and is tracked in issue #764 for resolution. | |
| qwen/qwen3.6-35b-a3b | — | — | A report that charmcraft V1.5.0 and V1.6.0 omitted the bash actions directory during bundling was confirmed as a known bug. The report was closed as a duplicate, with development and tracking moved to issue #764. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed as a duplicate. The missing bash actions directory in charmcraft V1.5.0 and V1.6.0 was confirmed by maintainers and superseded by issue #764, which now tracks the fix. |
Update history
No update history recorded yet.
Related work
-
Duplicate Of:
canonical/charmcraft#764
(confidence 97%)
Maintainer explicitly stated the work is tracked in #764 and closed this report as duplicated.
-
Superseded By:
canonical/charmcraft#768
(confidence 92%)
Merged PR 'Include an actions dir if present' (commit 5ada563c) fixing #764, i.e. the underlying defect reported here.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #35 charmcraft doesn't support actions | charmcraft | closed | Reported that charmcraft builds omitted actions.yaml, so charms with actions failed on install with 'CharmEvents' has no attribute. Fixed by merged PR #36 (commit a8cdb744), which makes 'charmcraft build' copy actions.yaml and config.yaml into the charm. | |
| #768 Include an 'actions' dir if present. | charmcraft | merged | Merged PR #768 (commit 5ada563c) to include an existing actions directory in packaged charms by default, fixing #764. | |
| #36 'charmcraft build' should pull in actions.yaml and config.yaml | charmcraft | merged | Merged PR #36 as commit a8cdb744, making charmcraft build automatically include actions.yaml and config.yaml in charm builds. | |
| #197 `charmcraft init` should not populate actions.yaml with real data | charmcraft | closed | charmcraft#197 was closed as abandoned after years of inactivity, with no recorded resolving PR or commit. | |
| #1114 config: support use actions in charmcraft.yaml | charmcraft | merged | Merged #1114 as commit 201b40f6, enabling actions in charmcraft.yaml and refactoring configuration models to avoid circular imports. | |
| #249 `charmcraft build` will let you build a charm that won't deploy | charmcraft | closed | Closed by facundobatista as a duplicate, tracking all build-time sanity checks (incl. config.yaml/actions.yaml validity) in the umbrella issue charmcraft#27; later implemented by merged PR #556 (a585aec6). | |
| #764 The `actions` directory is not being included by default | charmcraft | closed | Fixed by merged PR #768 (commit 5ada563c), which now includes an existing root actions directory in built charms. |