Skip to content

[CU-86b4umhm1] Update WyriHaximus/github-action-get-previous-tag action to v2#10

Open
dnastack-renovate[bot] wants to merge 1 commit into
mainfrom
renovate/wyrihaximus-github-action-get-previous-tag-2.x
Open

[CU-86b4umhm1] Update WyriHaximus/github-action-get-previous-tag action to v2#10
dnastack-renovate[bot] wants to merge 1 commit into
mainfrom
renovate/wyrihaximus-github-action-get-previous-tag-2.x

Conversation

@dnastack-renovate
Copy link
Copy Markdown

This PR contains the following updates:

Package Type Update Change
WyriHaximus/github-action-get-previous-tag action major v1.4.0v2.0.0

Release Notes

WyriHaximus/github-action-get-previous-tag (WyriHaximus/github-action-get-previous-tag)

v2.0.0

Compare Source

Migration

Migrating from prefix to pattern going from this:

prefix: foo-bar

To:

pattern: foo-bar*

Note the astrix (*) at the end. That was always added by default in the previous version. And is the default for pattern. But if you specify your own pattern and it used be a prefix, you MUST add the astrix (*) at the end. It's not suffixed by default anymore because we want to give you full controll over the pattern (after refs/tags/) so you can do things like semver (v*[0-9].*[0-9].*[0-9]) with it without us meddling with it.

v2.0.0

  • Total issues resolved: 0
  • Total pull requests resolved: 11
  • Total contributors: 4

Bug 🐞

Dependencies 📦

Feature 🏗

Enhancement ✨


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Development

Successfully merging this pull request may close these issues.

0 participants