Skip to content

Conversation

@adamtheturtle
Copy link
Member

@adamtheturtle adamtheturtle commented Jan 3, 2026

Use YAML block scalar syntax for replace field to fix zizmor warning.


Note

Adjusts the release workflow formatting to satisfy linting without changing behavior.

  • In .github/workflows/release.yml, updates the Update changelog step to use a YAML block scalar for replace (with a trailing newline) in jacobtomlinson/gha-find-replace@v3

Written by Cursor Bugbot for commit c90e8d4. This will update automatically on new commits. Configure here.

@adamtheturtle adamtheturtle enabled auto-merge (squash) January 3, 2026 08:52
replace: "Next\n----\n\n${{ steps.calver.outputs.release }}\n${{ steps.changelog_underline.outputs.underline\
\ }}"
replace: |-
Next\n----\n\n${{ steps.calver.outputs.release }}\n${{ steps.changelog_underline.outputs.underline }}\n
Copy link

Choose a reason for hiding this comment

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

Literal block scalar breaks newline escape sequences

The change from a double-quoted string to a YAML literal block scalar (|-) breaks the replace functionality. In double-quoted strings, \n is interpreted as an actual newline character. In literal block scalars, \n is preserved as the literal two characters (backslash and 'n'). The changelog file will be corrupted with literal \n text instead of actual line breaks. The find field still uses a double-quoted string with real newlines, creating a mismatch where matching will work but replacement will produce malformed output.

Fix in Cursor Fix in Web

@adamtheturtle adamtheturtle merged commit 0140f3d into main Jan 3, 2026
9 checks passed
@adamtheturtle adamtheturtle deleted the fix-zizmor-warning branch January 3, 2026 08:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants