v1.6.0-beta.2: Toolkit#command improvements

Some improvements to the Toolkit#command method:

• Run multiple times for multiple matches
• Pass the match array to the handler
• Improved docs

v1.6.0-beta.1: Toolkit#command improvements

What’s Changed

• Improvements to Toolkit#command, including better command matching and documentation.
• Mock process.on() in tests (#60) @JasonEtco

v1.6.0-beta.0: Toolkit#command

This is the first beta release containing a new method, Toolkit#command being worked on in #53. Still missing docs, but this beta release should help to test it out in real Actions.

v1.5.0

New feature

tools.log

A slightly customized instance of Signale, a great logging utility. You can use it in two ways: as tools.log(), or by picking the particular method.

tools.log('Logging something amazing!')
tools.log.info('Here is some information!')

Signale will output your logs to the Actions UI with some icons to help identify your logs:

I'm interested in your feedback on this feature!

What’s Changed

• Fix release workflow (#47) @JasonEtco
• Use external validate-semver-release action (#48) @JasonEtco
• Add Signale logger (#45) @JasonEtco

v1.5.0-beta.2

What’s Changed

Some additional changes to the Signale PR #45 that allow for a callable tools.log method:

tools.log('Hello!')
tools.log.info('Wow!')

v1.5.0-beta.1

New feature

This minor release (1.5.0) will include support for a logger - see #45 for the implementation! It's still missing documentation, hence the beta prerelease. I wanted to try it out in some real actions first!

Some basic docs:

tools.log.METHOD

So:

tools.log.info('Omg wow!')

v1.4.1

What’s Changed

The biggest change in this release is #44, which changes the behavior added in #36 to be a lot less aggressive. Thanks @banyan ❤️

• Update validate release action (#42) @JasonEtco
• Return neutral if skipped (#44) @banyan

v1.4.0

New features

tools.exit

A collection of methods to end the action's process and tell GitHub what status to set (success, neutral or failure). Internally, these methods call process.exit with the appropriate exit code. You can pass an optional message to each one to be logged before exiting. This can be used like an early return:

if (someCheck) tools.exit.neutral('No _action_ necessary!') 
if (anError) tools.exit.failure('We failed!')
tools.exit.success('We did it team!')

What’s Changed

• Publish tags from releases (#40) @JasonEtco
• Allow only a list of events (#37) @JasonEtco
• Add methods to exit an action (#39) @JasonEtco

v1.3.0

What’s Changed

• Defaults for store file path (#32) @JasonEtco
• Publish tags from releases (#40) @JasonEtco
• Allow only a list of events (#37) @JasonEtco

v1.2.1

What’s Changed

• Defaults for store file path (#32) @JasonEtco
• More Dockerfile comments (#32) @JasonEtco