ci: remove redundant version bump write permission - #937
Merged
marandaneto merged 1 commit intoSep 10, 2026
Conversation
Contributor
posthog-python Compliance ReportDate: 2026-09-10 09:12:02 UTC ✅ All Tests Passed!111/111 tests passed Capture_V1 Tests✅ 94/94 tests passed View Details
Feature_Flags Tests✅ 17/17 tests passed View Details
|
Contributor
|
Reviews (1): Last reviewed commit: "ci: remove redundant release contents pe..." | Re-trigger Greptile |
ioannisj
approved these changes
Sep 10, 2026
marandaneto
deleted the
ci/remove-redundant-release-permissions-20260910110030
branch
September 10, 2026 12:45
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.
💡 Motivation and Context
The
version-bumpjob grants the built-inGITHUB_TOKENrepository write access even though its repository writes use a separate GitHub App token.Lower
version-bumptocontents: read. Preserve the App-authenticated checkout and all App-token commit, tag and release operations. No authentication input or App permission changes.Read-only workflow inheritance remains allowed. This reduces the built-in token's permissions, not the job's separate App-token authority or build/publish exposure. No package release or changeset is needed.
💚 How did you test it?
actionlint -shellcheck= -pyflakes=andgit diff --checkpassed. Existing shell-lint diagnostics were checked against the baseline and left unchanged.📝 Checklist
If releasing new changes
No package release or changeset is needed.
🤖 Agent context
Autonomy: Human-driven (agent-assisted)
Implemented with Pi and delegate agents using file tools, Git, GitHub CLI, Python/PyYAML and actionlint. The parent agent reviewed the final diff. Work was performed in a dedicated worktree. Autoreview was skipped because all changes are GitHub workflow permission administration. No session transcript was published. Human review is required.