MartyBeGood / qmk_firmware

Open-source keyboard firmware for Atmel AVR and Arm USB families
https://qmk.fm
GNU General Public License v2.0
0 stars 0 forks source link

Bump anothrNick/github-tag-action from 1.46.0 to 1.61.0 #26

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps anothrNick/github-tag-action from 1.46.0 to 1.61.0.

Release notes

Sourced from anothrNick/github-tag-action's releases.

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

Suggested by @​vancejc-mt in anothrNick/github-tag-action#243

1.59.0: Hotfix - gitlog full breaking rebase and squash merges

The current implementation of full git log breaks in squash and rebase due missing HEAD using suggestion from @​jonavos here anothrNick/github-tag-action#232 and changing approach to compare log history.

Please report back to anothrNick/github-tag-action#232 if any further issues on use cases.

1.58.0: Exit with error if default branch is not set in non pr workflows

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 null

1.57.0: Skip bumps if there are no new commits in pre-release actrions re runs

Identified here anothrNick/github-tag-action#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.

1.56.0: Get the default branch from env vars also allow to overwrite as parameter

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 var

1.55.0: Select last commit or full branch history

This version allows to set BRANCH_HISTORY full|last for the history verification for finding bump comments. See pr for examples anothrNick/github-tag-action#218

1.53.0: Fixing repo tag bumps

Fixes action versioning bumps. From bug introduced in 1.50

1.52.0: A few hofixes

Improved tests. Warning for breaking change when renaming/refactoring output tag New output tag old_tag

What's Changed

Full Changelog: https://github.com/anothrNick/github-tag-action/compare/1.51.0...1.52.0

1.50.0: FIX to print actual tag to be used when using with_v in all scenarios

No release notes provided.

1.49.0: Fix branch wildcard issue and added major v1 tag

  • We can now reference uses: anothrNick/github-tag-action@v1 as uses: anothrNick/github-tag-action@1 fails due sha identification
  • Also we can now use again RELEASE_BRANCHES: '.*' or releases/* or similar.

1.48.0: Shellcheck improvements

  • Addresses shellcheck sanitizations during PR checks
Commits
  • 8c8163e Hotfix - Validate default_branch only when history type full (#244)
  • e286d60 Fix: small typo in readme (#241)
  • 6bebeb9 docs: add maintainers info (#239)
  • bb4fa8e Hotfix - Add log compare as default instead of full log (#237)
  • 2c9e17c Exit with error if default branch is not set in non prs (#235)
  • 39d8e88 Skip if there are no new commits in prerelease actions re-runs (#234)
  • 172098f Fix: Get the default branch from env vars also allow to overwrite as paramete...
  • 2fa4983 Select last commit or full branch history for analysis of #bumps (#218)
  • 11ca940 Revert "feat: pre-build dockerfile" (#220)
  • 8aac693 feat: build and push new prebuilt docker image (#219)
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
github-actions[bot] commented 1 year ago

Thank you for your contribution! This pull request has been automatically marked as stale because it has not had activity in the last 45 days. It will be closed in 30 days if no further activity occurs. Please feel free to give a status update now, or re-open when it's ready. For maintainers: Please label with bug, awaiting review, breaking_change, in progress, or on hold to prevent the issue from being re-flagged.

github-actions[bot] commented 1 year ago

Thank you for your contribution! This pull request has been automatically closed because it has not had activity in the last 30 days. Please feel free to give a status update now, ping for review, or re-open when it's ready. // [stale-action-closed]

dependabot[bot] commented 1 year ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.