v0.6.5

v0.6.5

v0.6.4

https://github.com/sociomantic-tsunami/beaver/milestone/23?closed=1

• dlang/d2-release: Mark repository as D2_ONLY #66

v0.6.3

https://github.com/sociomantic-tsunami/beaver/milestone/22?closed=1

v0.6.2

https://github.com/sociomantic-tsunami/beaver/milestone/21?closed=1

• Create .neptune.yml #60

v0.6.1

v0.6.1

v0.5.2

https://github.com/sociomantic-tsunami/beaver/milestone/20?closed=1

• install: Only remove .dockerignore if it wasn't present #59

v0.6.0

https://github.com/sociomantic-tsunami/beaver/milestone/17?closed=1

Features

The bintray upload command learned a dry run option

This is probably mainly only useful for testing.

The bintray upload command learned an option to force a Debian component

For projects that don't comply with SemVer/Neptune, there is a new beaver bintray upload option to override the Debian component to which the package
will be uploaded.

For example beaver bintray upload -C stable *.deb will upload packages to the
stable component instead of the default release/prerelease. No guessing
will be made at all, if you need to upload to different components based on
different conditions, you need to to the distinction yourself and run the
appropriate bintray upload -C <comp> command.

Most options can be set also via CLI

beaver

The beaver command and sub-commands take some options that need to be
propagated to other sub-commands via environment variables. This could be too
verbose and bloated for some use cases.

Now any environment variable that starts with BEAVER_ can be set via CLI. This
is done using a simple mapping, where beaver --some-option value is equivalent
to BEAVER_SOME_OPTION=VALUE beaver.

This kind of options can only be passed before a beaver command is specified
(so you can use beaver command --some-option value, you have to write it as
beaver --some-option value command.

v0.6.0-rc.2

Features

The bintray upload command learned a dry run option

This is probably mainly only useful for testing.

The bintray upload command learned an option to force a Debian component

For projects that don't comply with SemVer/Neptune, there is a new beaver bintray upload option to override the Debian component to which the package
will be uploaded.

For example beaver bintray upload -C stable *.deb will upload packages to the
stable component instead of the default release/prerelease. No guessing
will be made at all, if you need to upload to different components based on
different conditions, you need to to the distinction yourself and run the
appropriate bintray upload -C <comp> command.

Most options can be set also via CLI

beaver

The beaver command and sub-commands take some options that need to be
propagated to other sub-commands via environment variables. This could be too
verbose and bloated for some use cases.

Now any environment variable that starts with BEAVER_ can be set via CLI. This
is done using a simple mapping, where beaver --some-option value is equivalent
to BEAVER_SOME_OPTION=VALUE beaver.

This kind of options can only be passed before a beaver command is specified
(so you can use beaver command --some-option value, you have to write it as
beaver --some-option value command.

v0.6.0-rc.1

Features

The bintray upload command learned an option to force a Debian component

For projects that don't comply with SemVer/Neptune, there is a new beaver bintray upload option to override the Debian component to which the package
will be uploaded.

For example beaver bintray upload -C stable *.deb will upload packages to the
stable component instead of the default release/prerelease. No guessing
will be made at all, if you need to upload to different components based on
different conditions, you need to to the distinction yourself and run the
appropriate bintray upload -C <comp> command.

Most options can be set also via CLI

beaver

The beaver command and sub-commands take some options that need to be
propagated to other sub-commands via environment variables. This could be too
verbose and bloated for some use cases.

Now any environment variable that starts with BEAVER_ can be set via CLI. This
is done using a simple mapping, where beaver --some-option value is equivalent
to BEAVER_SOME_OPTION=VALUE beaver.

This kind of options can only be passed before a beaver command is specified
(so you can use beaver command --some-option value, you have to write it as
beaver --some-option value command.

v0.5.1

https://github.com/sociomantic-tsunami/beaver/milestone/18?closed=1

• dlang: Properly restore old shell flags #54