v5.4.0

• Updates to Node Version #133
• Update dependencies

v5.3.0

This version finally introduces a new branch-based versioning mode, version_from_branch, to support on-going releases. If enabled, the major and optionally minor version will always be taken from the branch, and only tags which match will be considered candidates. By default, any branch name format is allowed and will be used as the version so long as it ends with a major or major.minor version, e.g. release/v1 or release/1.2 or v1. This is an advanced feature and should really only be needed if you maintaining ongoing updates for previous versions. Additional documentation and an expanded user guide coming soon. With this release use_branches is deprecated and will be removed in v6.

Additionally, this release fixes a bug where prerelease mode was not working when bump each commit was enabled.

v5.2.1

Fix for diagnostic mode, build output was not included in action output.

v5.2.0

This release adds a "debug" mode to allow collection and replay of operations to aid troubleshooting when the source repository is unavailable.

v5.1.0

New Features

• (#69) Added a patch pattern for "bump each commit". If bump_each_commit_patch_pattern is set AND bump each commit mode is enabled, the patch version will only increment if the commit matches the specified patch pattern. Note that regex is supported using the JavaScript-like /pattern/ syntax. Flags are also supported using /pattern/I but there is no dedicated "flags" input. (This is the preferred method and the existing flags inputs for major and minor may be deprecated in a future release.)
• (#88) Added "prerelease mode" for repos which are still on 0.x.x version. If enabled this will treat "major" changes as "minor", preventing the 1.0.0 version from being automatically set. (It must be set manually) This is intended to help manage versioning for projects with a long pre-release timeline so that developers don't need to worry about the overall state of the project and can still indicate whether a particular commit is breaking or not.
• (#94) An output, is_tagged, indicates whether this commit was itself directly tagged. (Thanks @Kantis)
• (#92) Added outputs to provide information about the commit of the previous version.

Full Changelog: v5.0.3...v5.1.0

Fix for Prerelease Tagged Commits

Previously pre-release tags were detected as the "current tag", as the previously added tag validation was only apply to the tags from previous commits. This update adds this validation to the current commit.

Fix build output

• Fix for previous version not outputting current_commit

v5.0.1

Fixes for regular expression filters, thanks to @belcher-rok for finding this.

Version 5 GA Release

Version 5.0.0 is now available! Thank you to everyone who contributed to this release.

For more information, please refer to release notes for version 5.0.0 pre-releases.

Beta release 2

Fixes:

• Running action on a tagged commits produces correct value for previous_commit instead of 0.0.0.
• Prerelease tags are ignored when finding the last release tag