Repository navigation
MIP-0086: feat(bump-consumers): prepare without a key - #119
Merged
Merged
Conversation
…bot (MIP-0086 §5.6) bump-consumers splits in two: prepare clones each consumer, moves its pins and writes a patch with no token; publish applies the patches and opens the PRs as marola-merge-bot, in a job that runs no nix. A repo failing in prepare still lets publish handle the rest. merge-key-check gates the key's workflows through .github/merge-key-allowlist, and gemini.yml passes its secrets explicitly instead of `secrets: inherit`. Closes #80 Tested: scripts/bump-consumers.sh --self-test ok; merge_key_check.py . clean; release.py --check, actionlint; devkit-quality.sh (just quality body without Nix) rc=0 Co-Authored-By: Claude <[email protected]>
github-actions
Bot
changed the title
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.
bump-consumers splits in two: prepare clones each consumer, moves its pins and writes a patch with
no token; publish applies the patches and opens the PRs as marola-merge-bot, in a job that runs
no nix. A repo failing in prepare still lets publish handle the rest. merge-key-check gates the
key's workflows through .github/merge-key-allowlist, and gemini.yml passes its secrets explicitly
instead of
secrets: inherit.Closes #80
Tested: scripts/bump-consumers.sh --self-test ok; merge_key_check.py . clean; release.py --check, actionlint; devkit-quality.sh (just quality body without Nix) rc=0
Co-Authored-By: Claude [email protected]