Automate plugin submissions, labels and upstream release updates - #2
Merged
Merged
Conversation
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.
Plugin submissions now become catalog review PRs from immutable GitHub Release metadata. A workflow maintains eight labels, reconciles existing submissions, and checks already listed publishers every six hours for their latest stable release. Merging updates only the selected host catalog; plugin builds remain upstream.
The synchronizer validates tag/source identity, metadata and artifact SHA-256/size against GitHub records, host boundaries and immutable history. It never executes plugin code, merges its own proposals or admits changed publisher keys. Privileged events check out only main. English and Chinese guides describe setup, labels, legacy submissions and signed-feed boundaries.
Validation: 14 unit tests, both catalog validators, immutable-history checks, local Markdown links and git diff --check pass. Read-only validation of the actual OAuth v0.0.1 release matched all five artifact records. Automated PR creation requires the repository's standard Actions PR permission; workflow-created checks may need maintainer approval.
新增申请自动生成目录审核 PR,并自动维护状态标签;已收录插件每 6 小时检查最新稳定版。最终收录仍需维护者审核,不自动合并,不重新编译插件。