v4.0.1

ci(mergify): upgrade configuration to current format @[mergify[bot]](https://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: The delete_head_branch action 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) John C. Bland II (@johncblandii) (#60)

## what

• Bump the composite action's references to versions running on the Node 24 runtime, SHA-pinned
  with precise version comments:
  • actions/checkout@v4 → @3d3c42e5... # v7.0.1
  • actions/github-script@v7 → @3a2844b7... # v9.0.0 (×2)
  • release-drafter/release-drafter@v6 → @34d80673... # v7.7.0
• Pass token: ${{ inputs.token }} explicitly to the release-drafter step — v7 introduces a
  token input (defaulting to github.token); passing it explicitly guarantees the bot token is
  used regardless of how future versions weigh the input vs. the GITHUB_TOKEN env (the env is
  kept for back-compat)

why

• GitHub is deprecating the Node 20 runtime; steps pinned to node20 releases emit a deprecation
  warning for every consumer of this action (232 repos reference it)
• Combines and supersedes the three pending Renovate PRs (#59 checkout, #57 github-script,
  #56 release-drafter) in one reviewable change, upgraded to SHA pinning per the org's
  supply-chain direction (cloudposse/.github#261)
• Every new SHA was verified against its upstream tag, and runs.using: node24 confirmed at each
  pinned ref
• release-drafter v6→v7 breaking changes reviewed: the removed disable-releaser/disable-autolabeler
  inputs are not used here, and the org's auto-release*.yml configs use none of the dropped
  config keys (include-pre-releases, references)

references

• https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
• https://github.com/release-drafter/release-drafter/releases/tag/v7.0.0
• Supersedes #56, #57, #59