Skip to content

fix: update db backup release notes #422

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
adibarra merged 1 commit into from
Jun 5, 2026
Merged

fix: update db backup release notes #422

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/db-backup.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,5 +53,5 @@ jobs:
# $DUMP_GLOB is intentionally unquoted so the shell expands it to every part file.
gh release create "$TAG" $DUMP_GLOB \
--title "DB Dump $(date -u +%Y-%m-%d)" \
--notes "Weekly full database dump (xz-compressed, split into <2 GiB parts). Reassemble: cat *.tar.xz.part* | xz -d | tar -x" \
--notes "Weekly full database dump (xz-compressed, split into <2 GiB parts). Reassemble: `cat *.tar.xz.part* | xz -d | tar -x`" \
Copy link
Copy Markdown

@cursor cursor Bot Jun 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 84fcc7c. Configure here.

--latest=false