Skip to content

fix(action): Handle permission errors when updating publish issues #744

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
BYK merged 1 commit into from
Feb 6, 2026
Merged

fix(action): Handle permission errors when updating publish issues #744

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions action.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -282,9 +282,13 @@ runs:
${CHANGELOG_SECTION}"
if [[ -n "$existing_issue_number" ]]; then
# Update existing issue with fresh body (preserving checked target states)
gh issue edit "$existing_issue_number" -R "$PUBLISH_REPO" --body "$body"
echo "::notice::Updated existing publish request: ${existing_issue_url}"
# Try to update existing issue with fresh body (preserving checked target states)
# This may fail if the token doesn't have permission to update issues in the publish repo
if gh issue edit "$existing_issue_number" -R "$PUBLISH_REPO" --body "$body" 2>/dev/null; then
echo "::notice::Updated existing publish request: ${existing_issue_url}"
else
echo "::warning::Could not update existing issue (permission denied). Using existing issue as-is."
Copy link
Contributor

@cursor cursor bot Feb 6, 2026

Choose a reason for hiding this comment

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

All errors silently treated as permission errors

Medium Severity

The gh issue edit command's stderr is redirected to /dev/null, suppressing all error output, while the warning message assumes any failure is due to "permission denied". The command could fail for many other reasons (network issues, rate limiting, expired token, deleted issue, etc.), but the actual error is lost and a misleading message is shown instead. This makes debugging difficult when non-permission errors occur.

Fix in Cursor Fix in Web

fi
echo "issue_url=${existing_issue_url}" >> "$GITHUB_OUTPUT"
else
# Create new issue
Expand Down
Loading