Repository navigation
fix(release): 修复原生扩展校验与 WebExt 草稿发布 - #180
Merged
Merged
Conversation
- 区分开发依赖与真实 UI share，并在默认检查验证全部产物 - 使用 GitHub 草稿创建响应并保留版本与来源保护
This branch was successfully deployed
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.
当前第一方扩展发布在 Capture 0.2.1 的产物校验处停止：它没有消费 UI JavaScript，构建会省略 UI share，但旧校验把开发依赖误当成生产运行时依赖。本次允许未消费的 UI share 缺省，并继续拒绝重复 share、错误版本以及没有生产者版本声明的 share。Host 的单例配置和生产者自己的版本要求保持有效。
默认
pnpm check:package现在检查全部七个扩展的真实 MF 产物，并确认使用 UI 组件的 Twitter 仍有 UI share，所以本地与 PR CI 可以在合并前发现同类发布问题。同时，WebExt 创建草稿后直接使用 GitHub 创建接口返回的对象；上传后按 release ID 读取，避免新草稿尚未出现在列表时发布失败。针对 UI share 边界和新建草稿的三项回归检查、完整本地
pnpm check及全部七项 PR CI 均通过。另做了两次真实产物的受控违规：Capture 错误 UI 版本、Twitter 缺少已消费的 UI share 都被默认检查拒绝；恢复后检查通过。本次只改发布工具及其文档，不增加产品版本，不修改或覆盖已有公开 Release。合并后由受保护 main 的正常发布流程恢复尚未发布的七个 MF 版本。