Skip to content

Releases: craig-day/compute-tag

v5-pre.4

30 Mar 19:17
Compare
Choose a tag to compare
v5-pre.4 Pre-release
Pre-release

Automatic release of v5-pre.4

v5-pre.3

30 Mar 18:23
Compare
Choose a tag to compare
v5-pre.3 Pre-release
Pre-release

Automatic release of v5-pre.3

v5-pre.2

30 Mar 18:07
Compare
Choose a tag to compare
v5-pre.2 Pre-release
Pre-release

Automatic release of v5-pre.2

v5-pre.1

30 Mar 18:05
Compare
Choose a tag to compare
v5-pre.1 Pre-release
Pre-release

Automatic release of v5-pre.1

v5-pre.0

30 Mar 15:48
Compare
Choose a tag to compare
v5-pre.0 Pre-release
Pre-release

Automatic release of v5-pre.0

v4

29 Mar 03:32
Compare
Choose a tag to compare

Handle existing tags with or without the v character. If initial tags are created, they will always include v. i.e. it will be either v1 or v1.0.0 depending on the version scheme.

v3

29 Mar 01:55
Compare
Choose a tag to compare

Use the Github api to fetch information about existing tags instead of requiring them as inputs.

Breaking Changes

  • The input repository is now required.
  • The input github_token is now required.

New Features

  • You can specify which suffix gets added to a tag for a prerelease using the prerelease_suffix input.

v4-pre

29 Mar 03:29
Compare
Choose a tag to compare
v4-pre Pre-release
Pre-release

Automatic release of v4-pre

v3-pre

29 Mar 01:21
Compare
Choose a tag to compare
v3-pre Pre-release
Pre-release

Automatic release of v3-pre

v2

28 Mar 00:09
Compare
Choose a tag to compare

Handle the previous commit having a tag with a suffix.

For example, if the most recent tag is v2-pre, because v2 was never released, the new tag will be computed as v3-pre. This action favors moving forward in version numbers rather than having many variants of a single version number. In other words, it will go from v2-pre to v3-pre instead of v2-pre.1.