Update anothrNick/github-tag-action action to v1.71.0 #47
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.39.0
->1.71.0
Release Notes
anothrNick/github-tag-action (anothrNick/github-tag-action)
v1.71.0
Compare Source
What's Changed
New Contributors
Full Changelog: anothrNick/github-tag-action@1...1.71.0
v1.70.0
Compare Source
What's Changed
New Contributors
Full Changelog: anothrNick/github-tag-action@1...1.70.0
v1.69.0
Compare Source
v1.68.0
Compare Source
v1.67.0
: : improvements: tag strategy and tag listing for filteringCompare Source
Sorting tags by date [https://github.com/anothrNick/github-tag-action/pull/2722 ]
Adding GIT_API_TAGGING false option to switch to cli tagging [https://github.com/anothrNick/github-tag-action/pull/210](https://redirect.github.com/anothrNick/github-tag-action/pull/210)10 ]
CLI tagging nowdays is more reliable for github actions permissions.
v1.66.0
: : fixes: sigpipe 141 scenariosCompare Source
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.
v1.65.0
: : fixes pre-release tag existsCompare Source
Fixes a bug introduced in 1.64 that makes pre-releases error when following a release branch strategy.
More details here https://github.com/anothrNick/github-tag-action/issues/265
v1.64.0
: : hotfix: in some cases git rev errors since set -eCompare Source
v1.63.0
: : Improvements: set node to lts and catch actions errors efficientlyCompare Source
v1.62.0
: : More tests and outputs when default_bump set to NONECompare Source
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.
v1.61.0
: :Hotfix - Exclude validating the default branch when using branch_listory non fullCompare Source
Suggested by @vancejc-mt in https://github.com/anothrNick/github-tag-action/issues/243
v1.60.0
Compare Source
v1.59.0
: : Hotfix - gitlog full breaking rebase and squash mergesCompare Source
The current implementation of full git log breaks in squash and rebase due missing HEAD using suggestion from @jonavos here https://github.com/anothrNick/github-tag-action/issues/232#issuecomment-1372299198 and changing approach to compare log history.
Please report back to https://github.com/anothrNick/github-tag-action/issues/232 if any further issues on use cases.
v1.58.0
: : Exit with error if default branch is not set in non pr workflowsCompare Source
There are some cases where the
default_branch
is not available in the runner environment, This leads to no history of commits.This change attempts to identify the default branch in this scenarios and error the user if the attempt fails and
default_branch
remains nullv1.57.0
: : Skip bumps if there are no new commits in pre-release actrions re runsCompare Source
Identified here https://github.com/anothrNick/github-tag-action/issues/233 the action was not skipping bumps if there where no new commits in pre-release mode when an action is re run creating extra tags.
This minor change applies the same behavior used in normal releases.
v1.56.0
: : Get the default branch from env vars also allow to overwrite as parameterCompare Source
This is a feature from a hotfix where we add the option to specify a default branch from parameters else we capture the default branch from the runner
$GITHUB_BASE_REF
varv1.55.0
: : Select last commit or full branch historyCompare Source
This version allows to set BRANCH_HISTORY full|last for the history verification for finding bump comments. See pr for examples https://github.com/anothrNick/github-tag-action/pull/218
v1.54.0
Compare Source
v1.53.0
: : Fixing repo tag bumpsCompare Source
Fixes action versioning bumps.
From bug introduced in 1.50
v1.52.0
: : A few hofixesCompare Source
Improved tests.
Warning for breaking change when renaming/refactoring output
tag
New output tag
old_tag
What's Changed
Full Changelog: anothrNick/github-tag-action@1.51.0...1.52.0
v1.51.0
Compare Source
v1.50.0
: : FIX to print actual tag to be used when using with_v in all scenariosCompare Source
v1.49.0
: : Fix branch wildcard issue and added major v1 tagCompare Source
uses: anothrNick/github-tag-action@v1
asuses: anothrNick/github-tag-action@1
fails due sha identificationRELEASE_BRANCHES: '.*'
orreleases/*
or similar.v1.48.0
: : Shellcheck improvementsCompare Source
v1.47.0
Compare Source
v1.46.0
Compare Source
Reverted 1.45.0
v1.45.0
Compare Source
v1.44.0
Compare Source
v1.43.0
Compare Source
v1.42.0
Compare Source
What's Changed
New Contributors
Full Changelog: anothrNick/github-tag-action@1.41.0...1.42.0
v1.41.0
Compare Source
v1.40.0
Compare Source
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.