ci: fix Grok mirror bot push and release-please config - #8
Merged
Conversation
- The Grok mirror refresh commits to master, so its job needs contents: write (workflow default is read; the refresh pushed as github-actions[bot] and was denied with 403). - release-please rejects extra-files paths that escape the package dir (plugins/last9/../../.claude-plugin/...). Root plugin manifest versions become manually managed — marketplace installs key off git SHAs, not these fields.
prathamesh-sonpatki
added a commit
that referenced
this pull request
Aug 24, 2026
prathamesh-sonpatki
added a commit
that referenced
this pull request
Aug 24, 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
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.
Summary
Two master-push failures from the repo-as-hub landing (#6):
github-actions[bot]got 403 pushingplugins/last9/skillsbecause the workflow declarescontents: read. Job-scopedcontents: writeonsync-parityfixes it. The bot's pending change (dropping an orphaned mirror entry) lands on the next run.extra-filesentries pointing at root manifests viaplugins/last9/../..are rejected as illegal path traversal. Entries dropped: those two manifest versions become static (marketplace installs resolve via git SHA, so this is display-only metadata).Test plan
chore(grok):bot commit removing the orphaned mirror entry, followed by a green re-run.Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.