mirror of
https://github.com/EstrellaXD/Auto_Bangumi.git
synced 2026-11-05 23:18:56 +08:00
2ed46695a2
PR 检查打出的 zip 的 sha256 写进条目。合并后在独立 job 中重新打包的 zip、 签名 job 汇总的 zip（含复用的旧 zip）都必须与它一致才签名，构建在 PR 与 合并后产出不同字节时发布失败，不会签下未审查的内容。条目缺少或写错 sha256 时，PR 检查在摘要中给出应填的值。
1.4 KiB
1.4 KiB
Plugin
- id:
- repo:
- commit (40-char SHA):
- New plugin / update (old version -> new version):
Author checklist
- This PR changes only files under
plugins/registry/. commitis a full 40-character SHA, and it is pushed to a public repository.sha256matches the value in the CI summary (leave it out in the first push; CI shows it).- The file name equals the
idinplugin.toml. tests/has at least 1 test, and all tests pass.ab-plugin validatepasses.- For an update,
versionis higher than the listed version, andrepois unchanged. - If the plugin has a frontend, its source is in
web-src/withpackage.jsonandpnpm-lock.yaml. - The plugin depends only on the standard library and packages that AutoBangumi ships. Other pure-Python libraries are in
vendor/. - I agree that AutoBangumi redistributes the packed plugin in its release.
Maintainer review checklist
- I read all code at the compare link (update) or tree link (new plugin) in the Job Summary.
- The plugin connects only to documented hosts.
- The plugin writes nothing outside
config/. - If there is a frontend, I read
web-src/line by line. It runs on the main origin. - The declared
permissionsmatch what the code does.