fix(milestone-sync): suppress leaked API response bodies #5

Merged
neerdoc merged 1 commit from chore/cleanup into main 2026-07-15 14:44:20 +00:00
Owner

Five api_patch call sites weren't redirecting or capturing their response,
so the raw JSON leaked directly into the job log (confirmed live when
milestone PATCH responses showed up jammed onto the same line as the
'→ milestone state=...' message). issue-sync.sh and issue-intake.sh
already handled this correctly — only milestone-sync.sh had the gap.

Five api_patch call sites weren't redirecting or capturing their response, so the raw JSON leaked directly into the job log (confirmed live when milestone PATCH responses showed up jammed onto the same line as the '→ milestone state=...' message). issue-sync.sh and issue-intake.sh already handled this correctly — only milestone-sync.sh had the gap.
Five api_patch call sites weren't redirecting or capturing their response,
so the raw JSON leaked directly into the job log (confirmed live when
milestone PATCH responses showed up jammed onto the same line as the
'→ milestone state=...' message). issue-sync.sh and issue-intake.sh
already handled this correctly — only milestone-sync.sh had the gap.
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
WulfScience-FOSS/ci-actions!5
No description provided.