fix: revert Cargo.lock sync commit to plain git push#52
Merged
quiet-node merged 1 commit intomainfrom Apr 6, 2026
Merged
Conversation
The GitHub API approach failed with 'Argument list too long' because base64-encoding the full Cargo.lock inline as a shell argument exceeds the OS arg limit. Plain git commit + push works fine and the unverified badge on this bot commit is acceptable. Signed-off-by: Logan Nguyen <lg.131.dev@gmail.com>
quiet-node
added a commit
that referenced
this pull request
Apr 6, 2026
Removes the sync-cargo-lock job and the pr output added in PRs #43-#52. The release-please action started failing with 'Resource not accessible by integration' and the sync job is the only change to this workflow in that window. Reverting to the original two-job workflow to restore stability. Signed-off-by: Logan Nguyen <lg.131.dev@gmail.com>
quiet-node
added a commit
that referenced
this pull request
Apr 10, 2026
fix: revert Cargo.lock commit to plain git push The GitHub API approach failed with 'Argument list too long' because base64-encoding the full Cargo.lock inline as a shell argument exceeds the OS arg limit. Plain git commit + push works fine and the unverified badge on this bot commit is acceptable. Signed-off-by: Logan Nguyen <lg.131.dev@gmail.com>
quiet-node
added a commit
that referenced
this pull request
Apr 10, 2026
fix: revert Cargo.lock commit to plain git push The GitHub API approach failed with 'Argument list too long' because base64-encoding the full Cargo.lock inline as a shell argument exceeds the OS arg limit. Plain git commit + push works fine and the unverified badge on this bot commit is acceptable. Signed-off-by: Logan Nguyen <lg.131.dev@gmail.com>
quiet-node
added a commit
that referenced
this pull request
Apr 11, 2026
fix: revert Cargo.lock commit to plain git push The GitHub API approach failed with 'Argument list too long' because base64-encoding the full Cargo.lock inline as a shell argument exceeds the OS arg limit. Plain git commit + push works fine and the unverified badge on this bot commit is acceptable. Signed-off-by: Logan Nguyen <lg.131.dev@gmail.com>
This was referenced Apr 11, 2026
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.
Summary
Reverts the GitHub API approach for the Cargo.lock sync commit introduced in #50.
The
gh api PUTcall failed withArgument list too longbecause base64-encoding the full Cargo.lock inline as a shell argument ($(base64 -w 0 src-tauri/Cargo.lock)) exceeds the OS argument size limit. The plaingit commit+git pushapproach works correctly and the unverified badge on this bot commit is acceptable.Test plan
chore: sync Cargo.lock to version bumpcommit without errors🤖 Generated with Claude Code