Skip to content

Releases: PaulHatch/semantic-version

v5.0.0-beta

02 Nov 11:46
d2341ff
Compare
Choose a tag to compare
v5.0.0-beta Pre-release
Pre-release

What's Changed

  • Feat: support flags when using regexp by @colas31 in #65
  • Fixes set-output deprecation warnings in logs by @dusda in #67
  • Add version type output for #62

New Contributors

Full Changelog: v5.0.0-alpha2...v5.0.0-beta

Second Alpha Release for Version 5.0.0

15 Apr 16:09
Compare
Choose a tag to compare

This update includes a breaking change for version 5, versions will now be sorted using the version number rather than author date. This method should be more reliable overall for a large number of edge cases, however it comes with the caveat that if your tags are not in order for some reason, the "wrong" tag could be chosen. This change is part of a change to the method that fixes issues reported in issue 49, last version tag is incorrect where tags on commits immediately preceding merged branches were not detected.

This release also includes the additional metadata for issue #38.

Version 5.0.0

05 Apr 00:09
Compare
Choose a tag to compare
Pre-release

Version 5 is a full rewrite of semantic-version which restructures the action as a set of modular components, switching from JavaScript to TypeScript to make further development and extension easier by providing interfaces to implement distinct functions. This action started as a short, relatively opinionated script. As more features have been requested and added, this approach has proven insufficient. In version 5, functionality is implemented in three providers/resolvers that obtain the repository data, a classifier that interprets that data and produces the result data, and three formatters that transform the result into the version tag, the version string itself, and turns a list of commit authors into an output string. Overall this version is intended to be easier to extend, test, fork, and understand and contribute to.

Important Changes

  • A list of authors for a commit for a release are now included in the output, by default formatted as a CSV but JSON is also available, sorted in descending order of the number of commits they made since the last release. This can be useful to include in a release, for example as a Kubernetes annotation, to route alerts or allow a change author to be quickly contacted.
  • Commit message body can now be searched as well. This defaults to off right now to avoid breaking existing builds.
  • Short Tags support has been fully dropped. The tagging convention is not part of the semver spec and in retrospect I think I misunderstood how the most common conventions used. It may reappear in a future release. This is the only major breaking change.

This is an alpha release, feedback is appreciated.

Change Output Text

29 Oct 16:06
3d2ea28
Compare
Choose a tag to compare

Output version will now be created from the supplied version template.

Allow Slashes in Tag Prefixes

23 Apr 22:00
Compare
Choose a tag to compare

This release fixes an issue with tag prefixes that prevented them from containing a forward slash.

Fix for Short Tags Disabled

25 Feb 13:57
Compare
Choose a tag to compare

This version fixes an issue where certain "full" tags were not recognized when the short_tags flag was disabled.

Deprecate Branch Option

09 Feb 03:18
1afa8eb
Compare
Choose a tag to compare

This release (re)introduces support for HEAD as the branch parameter, which is now the default and recommended setting.

The branch setting should be considered deprecated and may be removed in a future release. If you have a use case that requires branch support, please open an issue.

Fix Tag Output

28 Jan 22:30
2909e6b
Compare
Choose a tag to compare

This version fixes the tag output to include the namespace if set.

Thanks to @dannysauer for this contribution.

Support for Regular Expressions

23 Jan 05:48
Compare
Choose a tag to compare
  • major_pattern and minor_pattern inputs now support regular expression if wrapped in /
  • Fix logic bug that prevented matching tags from being properly identified for increment calculations of tagged commits

Fix for Tagged Commits

17 Jan 00:43
Compare
Choose a tag to compare

This release fixes issue #16. When a commit is already tagged with a version at the time the action runs, that tag version is used, however previously this also caused the increment value to always be zero. With this change the increment value will be preserved only if the tagged version matches what the expected version would have been. If the tag applied to the current commit overrides the version expected, the increment will be set to zero since this is a new version.