ci: read-only build job, write token confined to the tag release job - #506
Merged
Conversation
Build and test ran pull-request code in a job holding a contents: write token that checkout also persisted into .git/config. Validation now runs in a read-only job with persist-credentials: false; packing, the NuGet push and the release upload move to a tag-gated job that alone gets contents: write. action-gh-release bumped to v3 for the current runner runtime. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Warning Review limit reachedNext included review available in 43 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Same hardening review feedback applied across the org's other package repos:
permissions: contents: read; build/test run PR code with no write token andpersist-credentials: falsereleasejob gated onstartsWith(github.ref, 'refs/tags/')withneeds: build— only that job getscontents: writesoftprops/action-gh-release@v3(v2 runs on the unsupported Node 20 runtime)Behavior on a version tag is unchanged: tests still gate the release, the package version still comes from the tag.
🤖 Generated with Claude Code