Skip to content

fix(workflows): remove unused issues: write and fix permission comments - #12

Merged
benhigham merged 1 commit into
mainfrom
fix/release-changesets-permissions
Mar 11, 2026
Merged

fix(workflows): remove unused issues: write and fix permission comments#12
benhigham merged 1 commit into
mainfrom
fix/release-changesets-permissions

Conversation

@benhigham

Copy link
Copy Markdown
Owner

Summary

  • Remove issues: write from release-changesets.yml — audited changesets/action source and found zero octokit.rest.issues.* calls, so this permission is unnecessary
  • Fix 4 permission comments to accurately describe what each permission is for and attribute it to the correct consumer (changesets/action vs npm publish)

Mirrors the fixes applied to commitlint-config in PR #49.

Test plan

  • Verify workflow YAML is valid (no syntax errors)
  • Confirm a release triggered by merging changesets still works end-to-end (creates version PR, publishes to npm with provenance)

…ents

Audited changesets/action source — zero octokit.rest.issues.* calls,
so `issues: write` is unnecessary. Updated remaining permission
comments to accurately attribute each to its consumer
(changesets/action vs npm publish).
Copilot AI review requested due to automatic review settings March 11, 2026 01:42
@benhigham
benhigham merged commit 930e355 into main Mar 11, 2026
6 checks passed
@benhigham
benhigham deleted the fix/release-changesets-permissions branch March 11, 2026 01:44

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Pull request overview

Updates the reusable Changesets release workflow to tighten permissions and improve the accuracy of permission rationale comments.

Changes:

  • Removes issues: write from the release job permissions.
  • Updates permission comments to better reflect which step/action needs each permission.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

id-token: write # for npm provenance verification (changesets/action)
issues: write # to post issue comments (changesets/action)
pull-requests: write # to create the pull request (changesets/action)
attestations: write # to persist npm provenance attestations (npm publish)

Copilot AI Mar 11, 2026

Copy link

Choose a reason for hiding this comment

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

The attestations: write permission/comment looks incorrect: nothing in this workflow references GitHub Attestations (no actions/attest-* step, and npm publish can’t use GitHub’s attestations API). If no step/action actually creates GitHub attestations, this permission should be removed; otherwise, update the comment to reflect the real consumer and why attestations: write is required.

Suggested change
attestations: write # to persist npm provenance attestations (npm publish)

Copilot uses AI. Check for mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants