This repository was archived by the owner on Mar 9, 2026. It is now read-only.
ci: add top-level permissions to workflow files#52
Merged
Conversation
Add explicit top-level `permissions` to 5 workflow files that were missing them, following GitHub Actions security best practices for least-privilege token scoping. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #52 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 3 3
Lines 22 22
Branches 6 6
=========================================
Hits 22 22 🚀 New features to boost your workflow:
|
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
Add explicit top-level
permissionsto 5 workflow files that were missing them, following GitHub Actions security best practices for least-privilege token scoping.Type of Change
Boundary Checklist (Required for Implementation Changes)
Security & API Stability
Security Impact:
contents: read)API Contract:
parsefunction signature, type definitions)ParseResult,ParseIssue, orIssueCodeVersioning:
Testing
Automated Checks:
bun run check:type:source)bun run test)bun run build)Additional Verification:
bun run checkpasses (lint + format)Changes
ci.ymlcontents: read;setupjob: addedcontents: read(job-level overrides top-level)wc-type-check.ymlcontents: readwc-lint-format.ymlcontents: readwc-test.ymlcontents: readwc-export-validation.ymlcontents: readSignature
🤖 Generated with Claude Code
Co-Authored-By: Claude noreply@anthropic.com