extension authors: adopt --strict, publish the action, verify the Release hooks (after #1487)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 20/100
调研方向
Start with docs/extension-registry.md and the linked work in #1487 and #1621. This issue spans release hooks, extension-template and registry workflows, action publishing, and a Codespaces or other-host check of Docker-in-Docker; several steps depend on a release and external organization settings. Done means completing the applicable checklist, verifying the release and template runs, and updating hosts.json when the version should become permanent.
由索引模型根据 Issue 内容生成。
描述
Left over from #1487. Everything here waits for the first release that contains the new tester and the Release hooks (they reach main with the next dev → main merge).
After that release
- Release hooks: the run after the Release workflow logged
told QueryaHub/extensionsandtold QueryaHub/extension-template(secretQUERYA_DISPATCH_TOKENis set). A manualRun workflowwith an already published version does the same check. In the registry aPublishrun byrepository_dispatchappears andcompat.jsongets a column for the version. - Template follow-up:
QueryaHub/extension-templatepushedquerya-<version>and opened a pull request (or an issue, if the organization still forbids Actions to open pull requests). Merge it, and check that the Test run on the branch is green. -
--strictis in the tester (#1621). InQueryaHub/extension-templatereplace the "Fail if the plugin ran without the sandbox" JUnit grep withstrict: "true"of the action, and the same inQueryaHub/extensions(.github/actions/test-record). - Publish
QueryaHub/action-test-extension@v1(a copy of.github/actions/test-extension, now withstrict), then point the template and the registry at it instead ofQueryaHub/Querya-Desktop/.github/actions/test-extension@<sha>. - Raise
hosts.jsoninQueryaHub/extensionswhen the new version should become a permanent column ofcompat.json.
Not done and not blocked by a release
-
devcontainer upon the template, with Docker-in-Docker and the compose file, ending in a greenquerya-ext-tester ./dist --connect ... --sandbox, was only checked in parts (the Feature installs and the tester passes in the container; the nested Docker daemon did not start on a host without the iptables nat table). Check it in Codespaces or on another host. - Optional: let GitHub Actions open pull requests in the organization (Settings → Actions → General), so the template's release pull request is not an issue.
- Optional: replace the personal access token behind
QUERYA_DISPATCH_TOKENwith a GitHub App token, so the hooks do not stop when the person or the token expires.
- 主要语言
- Dart
- 星标
- 23
- 派生
- 1
- 平均合并
- 31 分钟
- 30 天内合并 PR
- 570
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
QueryaHub/Querya-Desktop 的其他 Issue
-
enhancement ui
难度 2/5 1-3 小时 新手友好度 78/100
QueryaHub/Querya-Desktop#1689 ·
维护者通常 1 天内回复
-
ui(dialogs): make destructive query and DML preview dialogs adaptive and prevent table name overflow未关闭bug frontend
难度 2/5 1-3 小时 新手友好度 82/100
QueryaHub/Querya-Desktop#1642 ·
维护者通常 1 天内回复
-
bug error-handling settings
难度 1/5 1-3 小时 新手友好度 78/100
QueryaHub/Querya-Desktop#1637 ·
维护者通常 1 天内回复
-
enhancement
难度 1/5 1 小时以内 新手友好度 88/100
QueryaHub/Querya-Desktop#1636 ·
维护者通常 1 天内回复
-
enhancement marketplace
难度 2/5 1-3 小时 新手友好度 78/100
QueryaHub/Querya-Desktop#1635 ·
维护者通常 1 天内回复
查看 QueryaHub/Querya-Desktop 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 74/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 67/100
PhoebeSoftware/xrooster#41 ·
-
难度 2/5 1-3 小时 新手友好度 83/100
VeryGoodOpenSource/very_good_templates#665 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
VeryGoodOpenSource/very_good_cli#1783 ·
维护者通常 1 天内回复
-
bug to check
难度 2/5 1-3 小时 新手友好度 66/100
维护者通常 1 天内回复