Fix release workflow

[ilopezluna]

No description provided.

[gemini-code-assist]

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

[sourcery-ai]

Hey - I've found 1 issue, and left some high level feedback:

• The use of base64 -w 0 is GNU-specific and will fail on macOS/BSD runners; if this workflow might ever run outside of GNU coreutils, consider a more portable approach (e.g., base64 | tr -d '\n') or explicitly constrain the job to a GNU environment.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The use of `base64 -w 0` is GNU-specific and will fail on macOS/BSD runners; if this workflow might ever run outside of GNU coreutils, consider a more portable approach (e.g., `base64 | tr -d '\n'`) or explicitly constrain the job to a GNU environment.

## Individual Comments

### Comment 1
<location> `.github/workflows/release.yml:443` </location>
<code_context>
         run: |
           # Read release notes, base64-encode to safely pass multiline content
-          NOTES_B64=$(base64 < release-notes.md)
+          NOTES_B64=$(base64 -w 0 < release-notes.md)
           echo "changelog_b64=$NOTES_B64" >> "$GITHUB_OUTPUT"

</code_context>

<issue_to_address>
**issue (bug_risk):** Consider portability of `base64 -w 0` across different runner environments.

`-w` is a GNU-specific `base64` flag and isn’t available on macOS/BSD. If this workflow ever runs on a non-GNU runner (e.g., self-hosted macOS), this step will fail. A portable approach is:

```sh
NOTES_B64=$(base64 < release-notes.md | tr -d '\n')
```

This avoids line wrapping without relying on GNU-only options.
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}