ci: name release version-stamp step for readability

[MGPOCKY]

Problem

In .github/workflows/release.yml, the branch-only version stamp run step is unnamed and longer than 300 characters. In the GitHub Actions UI that collapses into a generic label, which hurts readability when package.json / jsr.json version updates fail.

Changes

Semantics are unchanged: same if: condition and the same jq / mv commands.

• Add name: Stamp package.json and jsr.json with dev version

Test plan

• Confirm the step still runs only when github.ref_type == 'branch'
• Confirm both JSON files still get the same -dev.<run>+<sha> suffix
• Confirm the step shows the new name in the Actions UI

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
es-toolkit	Ready	Preview	Aug 1, 2026 5:32am

[Copilot]

Pull request overview

Improves GitHub Actions UI readability by naming the previously unnamed branch-only version-stamping step in the release workflow, without changing its behavior.

Changes:

• Add a descriptive name to the branch-only step that stamps package.json and jsr.json with the -dev.<run>+<sha> suffix.
• Keep the existing if: github.ref_type == 'branch' condition and jq/mv commands unchanged.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.