nas/Auto_Bangumi
1
0
Fork 0
mirror of https://github.com/EstrellaXD/Auto_Bangumi.git synced 2026-10-31 12:45:41 +08:00
Code Issues Packages Projects Releases Wiki Activity
Files
4.0-dev
Auto_Bangumi/.github/PULL_REQUEST_TEMPLATE/plugin.md
Estrella Pan b129c4437a chore(release): 准备 4.0.0 
- 部署文档、升级指南与 README 改为正式版说法：latest = 4.0，3.3 固定为 3.3.7
- docs/changelog/4.0.md 新增 4.0.0 汇总（升级前必读、破坏性变更、新功能、主要修复），链接改为绝对地址
- 文档站与插件市场改为从 main 发布，插件上架 PR 的目标分支改为 main
- 文档站页脚版本 v4.0.0；en/ja README 的 star history 地址
2026-10-24 11:46:50 +02:00

1.4 KiB
Raw Permalink Blame History

Plugin

  • id:
  • repo:
  • commit (40-char SHA):
  • New plugin / update (old version -> new version):

Author checklist

  • This PR changes only files under plugins/registry/.
  • commit is a full 40-character SHA, and it is pushed to a public repository.
  • sha256 matches the value in the CI summary (leave it out in the first push; CI shows it).
  • The file name equals the id in plugin.toml.
  • tests/ has at least 1 test, and all tests pass.
  • ab-plugin validate passes.
  • For an update, version is higher than the listed version, and repo is unchanged.
  • If the plugin has a frontend, its source is in web-src/ with package.json and pnpm-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 permissions match what the code does.
Reference in New Issue View Git Blame Copy Permalink