chore: release action improvements

[romange]

1. fix action version
2. set more options to avoid coincedental overrides of the releases

[augmentcode]

🤖 Augment PR Summary

Summary: Improves the tag-triggered release workflow by pinning ncipollo/release-action and tightening release update behavior to reduce accidental overwrites.
Changes: Adds safeguards/flags (e.g., skipIfReleaseExists, updateOnlyUnreleased, generateReleaseNotes) and fixes the dfly_bench artifact glob for ARM uploads.

_{🤖 Was this summary useful? React with 👍 or 👎}

[Copilot]

Pull request overview

Updates the GitHub Actions release workflow to pin the release-action version and adjust release creation/update behavior to reduce unintended overwrites during tag-based releases.

Changes:

• Pin ncipollo/release-action to v1.21.0 (instead of @v1) in release creation and publishing steps.
• Add release-action options intended to avoid accidental updates/overrides (skipIfReleaseExists, updateOnlyUnreleased, generateReleaseNotes, commit).
• Tighten the dfly_bench artifact glob to dfly_bench-*.tar.gz.

[augmentcode]

Review completed. 2 suggestions posted.

Comment augment review to trigger a new review at any time.

[augmentcode]

.github/workflows/release.yml:28 — Per the action README, commit is only used when the tag does not exist; since this workflow runs on a tag push, this input may be redundant and could be misleading if the intent was to control the release’s target commitish.

Severity: low

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

[augmentcode]

.github/workflows/release.yml:189 — Now that create-release enables generateReleaseNotes, this later allowUpdates run may unintentionally clear the existing release notes body unless the body is explicitly omitted/preserved during updates (e.g., via the action’s omit-body-during-update option).

Severity: medium

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}