fix: encode binary content over rest api with base64 instead of utf-8#53
Merged
fix: encode binary content over rest api with base64 instead of utf-8#53
Conversation
avidal
force-pushed
the
avidal/fix-binary-push
branch
from
aa82ed2 to
2557dfa
Compare
In the switch to v3, when the REST API was brought in, there was a bug where binary content was pushed via the REST API using utf-8 encoding instead of base64, which then triggered a downstream issue: the action release process uses commit-headless to push the built binaries into `dist/`, and these binaries were then treated as shell scripts.
avidal
force-pushed
the
avidal/fix-binary-push
branch
from
2557dfa to
0d62a3b
Compare
github-actions Bot
added a commit
that referenced
this pull request
Apr 7, 2026
…of utf-8 (#53) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In the switch to v3, when the REST API was brought in, there was a bug where binary content was pushed via the REST API using utf-8 encoding instead of base64, which then triggered a downstream issue: the action release process uses commit-headless to push the built binaries into
dist/, and these binaries were then treated as shell scripts.