fix: update db backup release notes

[adibarra]

Note

Low Risk
Cosmetic change to release note text in an existing workflow; no database or application runtime impact.

Overview
Updates the Create release step in the database backup workflow so the reassembly shell one-liner in gh release create --notes is wrapped in backticks for GitHub-flavored markdown (inline code in the release body).

No changes to dump, compress, split, or upload behavior—only the text shown on weekly DB dump releases.

^{Reviewed by Cursor Bugbot for commit 84fcc7c. Bugbot is set up for automated code reviews on this repo. Configure here.}

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
inferencemax-app	Building	Preview, Comment	Jun 5, 2026 10:33pm

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 84fcc7c. Configure here.}

[cursor]

Backticks run shell substitution

High Severity

The --notes string uses backticks around the reassembly command inside double quotes in a bash run step. Bash treats those backticks as command substitution, so the workflow runs cat *.tar.xz.part* | xz -d | tar -x when creating the release instead of putting literal backticks in the GitHub release notes.

 

^{Reviewed by Cursor Bugbot for commit 84fcc7c. Configure here.}