chore(deps): update changesets/action digest to 04d574e

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
changesets/action	action	digest	e0145ed → 04d574e

---

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: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

---

Summary by cubic

Updates the pinned digest for changesets/action in .github/workflows/bump.yml to 04d574e to keep the bump workflow deterministic and pick up upstream fixes. Merges the latest canary; no other changes.

^{Written for commit d284d8d. Summary will update on new commits.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: d284d8d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
react-email	Ready	Preview, Comment	Mar 4, 2026 7:37pm
react-email-demo	Ready	Preview, Comment	Mar 4, 2026 7:37pm

[socket-security]

No dependency changes detected. Learn more about Socket for GitHub.

👍 No dependency changes detected in pull request

[cubic-dev-ai]

No issues found across 1 file

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.