Installation

1. Add :expublish to your dev dependencies in mix.exs:

{:expublish, "~> 2.3", only: [:dev]}

2. Create a CHANGELOG.md in the root folder of your project. It must contain a placeholder:

<!-- %% CHANGELOG_ENTRIES %% -->

3. Put the following line in your .gitignore:

RELEASE.md

Alternatively you may keep the RELEASE.md inside version control and use it when publishing from CI. The file is deleted after every succesful release.

4. (Optional) While writing the final package version, Expublish expects the version to be located where mix initially placed it.

As it is quite common to keep the package version in a module attribute inside mix.exs, Expublish will consider this as well.

@version "1.0.0"
# ...
version: @version

If the package version is maintained in a separate file, expublish can be made aware of that with the appropriate option: --version-file=VERSION.txt where VERSION.txt is a file like:

1.0.0

Hex auth

Regardless of publishing to hex.pm or a self-hosted hex repository, the shell environment where mix expublish is being executed must authenticate for the publishing step to succeed.

While publishing to hex.pm usually requires a valid HEX_API_TOKEN to be defined in the current environment, self-hosted repositories can use a range of various authentication methods.

Check the hex documentation on publishing and self-hosting to find out more.

Prerequisites

Expublish expects git and mix to be available at runtime but comes without any additional dependencies.