ci: dependabot version updates + least-privilege workflow permissions - #46
Merged
Merged
Conversation
- .github/dependabot.yml: weekly github-actions (grouped) + pip update checks - ci.yml / publish.yml: explicit top-level 'permissions: contents: read' (publish job keeps its scoped 'id-token: write' for PyPI trusted publishing) Companion to repo-settings changes enabled via API: secret scanning + push protection, CodeQL default setup (python + actions).
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
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.
What
Repo-file half of the security/quality setup pass:
.github/dependabot.yml— weekly version-update checks forgithub-actions(grouped into one PR; covers.github/workflows/and the root compositeaction.yml) andpip(runtime is stdlib-only; watches the optional extras and any future pins).ci.yml/publish.yml— explicit top-levelpermissions: contents: readso the workflow token is least-privilege regardless of repo/org default drift. Thepublishjob keeps its scopedid-token: writefor PyPI trusted publishing; same-run artifact download/upload uses the runtime token, so noactions: readneeded.Companion settings (already enabled via API, not in this diff)
python+actions)Test plan