Releases: canonical/charmcraft
Release 0.7.0
-
Added support for Charm Libraries, a mechanism to easily share and reuse charm interfaces and other components (tutorial)
-
Initial support for charm bundles: the 'pack' command.
-
Better project bootstrapping in 'init': can be used in a non-empty directory and adds coverage to the project tests.
Release 0.6.1
-
Improved and polished texts, help and error messages, etc.
-
Support to create a library, first step in the charm libraries lifecycle.
Release 0.6.0
-
Improved the template for new charms: now they use the testing harness in the modern way.
-
Refactored the commands infrastructure for improved process bootstrapping and UX consistency.
-
Small UX improvements in messages and help texts.
Release 0.5.0
-
Include the
version
file in the built charm (to be used by Charmhub). -
Now the
revision
is a mandatory parameter of therelease
command. -
Refactored help messages and indications.
-
Better explanation in the README on how to run the project directly from Github.
Release 0.4.0
-
Changed which files and directories are considered for a build: now
everything is included in the charm, except what is explicitly marked as
to ignore by Juju (which can be controlled through the.jujuignore
file). -
Improved commands structure: each now has a long description and accepts
the--verbose
and--quiet
global options -
Cope with conflicting command line arguments when using system pip3 from
Ubuntu Bionic and earlier when building -
Several improvements to
charmcraft init
, including --series and an
improved README.
0.3.1
- Support API changes in Store responses (old and new versions of a couple of renamed fields).
0.3.0
-
New 'init' command to populate an empty directory with the scaffolding for a new charm.
-
Basic but complete interaction with the Store, to authenticate, register and list names, and upload and release revisions (working with staging for now).
-
Commands and their options are autocompleted now (hitting tab, as usual).
-
Improvements when building charms: include the 'template' directory and support hooks that link the charm directly.
-
Clearer tracking of project version.
0.2.0
Release notes:
-
Charmcraft is now packaged as a snap (try it with
snap install --edge charmcraft
). -
First interaction with the Store: now Charmcraft can authenticate against staging.
-
All debug information (what you would see in the terminal with
--verbose
) is now always sent to a log file (which is indicated if an error happens, and left there for forensics). -
Improvements when the user interrupts the program (Ctrl-c) and in return codes in general.
-
Better debugging information when building a charm.