ci: harden workflows with pinned actions and least-privilege permissions - #187
Open
ahmed-tarek-salem wants to merge 7 commits into
Open
ci: harden workflows with pinned actions and least-privilege permissions#187ahmed-tarek-salem wants to merge 7 commits into
ahmed-tarek-salem wants to merge 7 commits into
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
The dev/staging ruleset now lets the qubic-release-bot App bypass the PR review requirement (bypass_mode: pull_request), so the staging rc release PR can be merged hands-free. main stays human-gated (classic protection, no App bypass), so production is unaffected. Adds the auto-merge step and updates the comment that previously said staging was human-merged.
sallymoc
approved these changes
Aug 13, 2026
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
3 participants
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.
Security hardening
permissions({}by default, per-job grants) across commitlint / lint-pr / deploy / refresh-smart-contractsconcurrencyguards added to commitlint / deploy / refresh-smart-contracts${{ }}expressions moved out ofrun:intoenv:protocol: ftps(the action defaults to plaintext FTP, so credentials were crossing the wire in the clear)Release automation: semantic-release → release-please
semantic-release, its 7 devDependencies and.releasercremoved;release-pleaseconfig + manifests added, seeded at the current1.28.0chore(release): X.Y.ZPR that a human reviews and mergesRELEASE_APP_ID/RELEASE_APP_PRIVATE_KEY), scoped to contents + pull-requests. No SSH deploy key, no ruleset bypass.Gated production deploys
deploy.ymlnow handlesdev/stagingonlyrelease-please.yml, only when a stable release is actually cut (release_created == 'true'), behind theproductionenvironment (required reviewers + prevent self-review), so an rc can never reach production