Update cloudposse/github-action-auto-release action to v4.0.1 - #268
Open
renovate[bot] wants to merge 1 commit into
Open
Update cloudposse/github-action-auto-release action to v4.0.1#268renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
requested review from
Veronika Gnilitska (gberenice) and
John C. Bland II (johncblandii)
August 13, 2026 20:50
|
Important Cloud Posse Engineering Team Review RequiredThis pull request modifies files that require Cloud Posse's review. Please be patient, and a core maintainer will review your changes. To expedite this process, reach out to us on Slack in the |
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
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:
v4.0.0→v4.0.1Release Notes
cloudposse/github-action-auto-release (cloudposse/github-action-auto-release)
v4.0.1Compare Source
ci(mergify): upgrade configuration to current format @[mergify[bot]](https://redirect.github.com/apps/mergify) (#58)
Hey there! 👋We've noticed that your Mergify configuration is using some deprecated fields.
No worries—we've got your back! This automated PR updates your config to align with the newest standards, ensuring everything keeps running smoothly.
Do not procrastinate! You must upgrade your configuration before 2026-07-31, otherwise your configuration will stop working.
What's Changed?
pull_request_rules → actions → delete_head_branch: Thedelete_head_branchaction is deprecated. Use GitHub's native 'Automatically delete head branches' setting instead: https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches (deadline: 2026-07-31)Why This Matters
Keeping your configuration up-to-date means you'll benefit from the latest features and improvements Mergify has to offer. Plus, it helps prevent any unexpected hiccups down the road.
Got Questions? We've Got Answers! 🙌
Is this update safe to merge?
Absolutely! We've made sure the changes are compatible with your current setup. Your workflows should continue to work just as before—if not better!
Do I need to do anything special after merging?
Nope! Just merge this PR, and you're all set. If you have any custom configurations, it's a good idea to give them a quick look to ensure everything's in order.
What if I run into issues or have concerns?
We're here to help! Feel free to reach out to our support team anytime.
Thanks for being awesome and keeping your configuration up-to-date! If you have any thoughts or need a hand, don't hesitate to let us know.
Happy merging! 🎉
🚀 Enhancements
chore: upgrade actions to Node 24 runtime (SHA-pinned) @johncblandii (#60)
what
with precise version comments:
actions/checkout@v4→@3d3c42e5...# v7.0.1actions/github-script@v7→@3a2844b7...# v9.0.0(×2)release-drafter/release-drafter@v6→@34d80673...# v7.7.0token: ${{ inputs.token }}explicitly to the release-drafter step — v7 introduces atokeninput (defaulting togithub.token); passing it explicitly guarantees the bot token isused regardless of how future versions weigh the input vs. the
GITHUB_TOKENenv (the env iskept for back-compat)
why
warning for every consumer of this action (232 repos reference it)
#56 release-drafter) in one reviewable change, upgraded to SHA pinning per the org's
supply-chain direction (cloudposse/.github#261)
runs.using: node24confirmed at eachpinned ref
disable-releaser/disable-autolabelerinputs are not used here, and the org's
auto-release*.ymlconfigs use none of the droppedconfig keys (
include-pre-releases,references)references
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.