canonical/charmcraft

AI Summary: This GitHub issue requests an improvement to the `charmcraft release` command's output or Charmhub's response when resources associated with a charm are automatically released. Currently, Charmhub implicitly releases resources if they were part of previous charm revisions, but the user experience regarding this automatic action needs to be made more explicit or informative.

AI Summary: This issue proposes simplifying the `ResourceOption` class in `charmcraft/utils/cli.py`. The current implementation requires instantiation followed by a call, which is considered hard to read. The goal is to refactor it into a straightforward class directly used by the CLI, similar to an example provided from the `snapcraft` project.

AI Summary: This GitHub issue proposes testing whether requiring `libyaml-devel` on yum-based systems (like AlmaLinux) enables charms to correctly use YAML. It involves creating and deploying a test charm that utilizes YAML, then deciding to either add `libyaml-devel` as a dependency for consistency or close the issue with an explanation if it doesn't work.