Skip to content

Releases: anothrNick/github-tag-action

1.71.0

23 Sep 11:44
f278d49
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 1...1.71.0

1.70.0

08 Jul 15:21
777684d
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 1...1.70.0

1.67.0: improvements: tag strategy and tag listing for filtering

13 Jun 21:24
a2c70ae
Compare
Choose a tag to compare

Sorting tags by date [ https://github.com//pull/272 ]
Adding GIT_API_TAGGING false option to switch to cli tagging [ https://github.com//pull/210 ]

CLI tagging nowdays is more reliable for github actions permissions.

1.66.0: fixes: sigpipe 141 scenarios

21 May 22:26
72703d0
Compare
Choose a tag to compare

In some cases if the repo contains hundreds of tags, since we set -e grep combined with git tag reads randomly exits with error 141.

1.65.0: fixes pre-release tag exists

15 May 10:24
94666f1
Compare
Choose a tag to compare

Fixes a bug introduced in 1.64 that makes pre-releases error when following a release branch strategy.
More details here #265

1.64.0: hotfix: in some cases git rev errors since set -e

12 May 03:33
c360518
Compare
Choose a tag to compare
Fix: tag_commit on fresh repo with no tags (#261)

1.63.0: Improvements: set node to lts and catch actions errors efficiently

10 May 22:37
72f3a54
Compare
Choose a tag to compare
Update to node 18 and set bash -e for error catching (#258)

1.62.0: More tests and outputs when default_bump set to NONE

10 Apr 03:21
d77194f
Compare
Choose a tag to compare

This is a very minor release, adds outputs to workflows using default_bump none when there are no #comments found that trigger a commit bump.

1.61.0:Hotfix - Exclude validating the default branch when using branch_listory non full

06 Jan 18:03
8c8163e
Compare
Choose a tag to compare

1.59.0: Hotfix - gitlog full breaking rebase and squash merges

05 Jan 21:01
bb4fa8e
Compare
Choose a tag to compare

The current implementation of full git log breaks in squash and rebase due missing HEAD using suggestion from @jonavos here #232 (comment) and changing approach to compare log history.

Please report back to #232 if any further issues on use cases.