Repository navigation
Auto-publish team plugin updates with unchanged permissions - #18
Merged
Merged
Conversation
…nged - sync.sh: team plugin, existing entry, no new-permissions label -> commit to main and start Publish; falls back to a pull request when main refuses the push - regtool keeps the manifest's platforms (core 0.6.1) in entries and the catalog - CORE_REF v0.6.2 so platforms and per-entry platforms validate - docs: new release flow, REGISTRY_TOKEN, branch protection bypass Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YBUx1d4niJfMeuwPGpikuu
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
2 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.
What
teamplugin that adds no permissions (nonew-permissionslabel) and is not the plugin's first version is committed straight tomain, then Publish is started (gh workflow run, since GITHUB_TOKEN pushes don't trigger workflows). Ifmainrejects the push it falls back to the usual PR. Community plugins, first versions and permission changes still go through a reviewed PR.sync.yml:actions: writepermission;repository_dispatch: plugin-release(already there) is now sent by the plugin release workflow.platformsfield into entries and the catalog, and checks it against the reviewed entry.platformsvalidate.REGISTRY_TOKEN, branch-protection bypass) and CONTRIBUTING.Needs, once
REGISTRY_TOKEN(fine-grained, Ervisio/plugins, Contents: read & write) for instant pickup.mainis protected: add GitHub Actions to the bypass list, otherwise auto updates fall back to PRs.Checked:
go vet/go testfor regtool,shellcheck -x scripts/*.sh.🤖 Generated with Claude Code
https://claude.ai/code/session_01YBUx1d4niJfMeuwPGpikuu
Generated by Claude Code