Update mukunku/tag-exists-action action to v1.6.0 #91
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/mukunku-tag-exists-action-1.x
branch
from
0ff6420 to
c4bc01f
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/mukunku-tag-exists-action-1.x
branch
from
c4bc01f to
2e8d72f
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/mukunku-tag-exists-action-1.x
branch
from
2e8d72f to
95beaf8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
v1.0.0->v1.6.0Release Notes
mukunku/tag-exists-action (mukunku/tag-exists-action)
v1.6.0: Upgrade from Node16 to Node20Compare Source
This release bumps the node runtime version.
Thanks to @davidgamero for putting the PR together (#24)
v1.5.0: Better edge case error handlingCompare Source
This release updates packages and adds more comprehensive error handling.
Thanks to @kroese for their contribution to this release ⭐ (#21)
v1.4.0: New optionalrepoparameterCompare Source
This release exposes a new optional
repoparameter. With this you may check the existence of tags in any repo you have access to. Not just the repo the action is running in.Special thanks to @zachgoncalves for implementing this feature that was requested in #18 🥇
v1.3.0: Upgrade @actions/github to 5.1.1Compare Source
This release updates all package dependencies to their latest versions. Most notably upgrading the
@actions/githubpackage from 2.1.1 to 5.1.1v1.2.0: Automatic GITHUB_TOKEN InjectionCompare Source
With this release users no longer need to provide a
GITHUB_TOKENenvironment variable to the action.Special thanks to @kzrnm (#8)
v1.1.0: Upgraded from Node12 to Node16Compare Source
This release bumps a bunch of package versions and the node runtime version.
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.
This PR was generated by Mend Renovate. View the repository job log.