Conversation
…la-plugin .Build 决定的是**插件作者编译时看到的那份契约**,与契约同版本发布才对 —— 所以它连同端到端 冒烟(scripts/Invoke-Smoke.ps1 + tests/smoke/)一起搬去了 VelaShellLabs/velashell-plugin-sdk。 插件工程出包用的打包器也在那边自带(VelaShell.PluginSdk.Packer,走同一个 VpxContainer)。 **本仓库因此没有任何下游**:vela-plugin 是面向人的完整工具(商店、开发内环、签名、体检), 发不发版与插件作者能不能 `dotnet build -t:PackVpx` 出包毫无关系。 - CI / release 只打一个包,冒烟步骤删掉 - 插件生态那个 Avalonia 版本锁的副本与它的构建期核对(VELA1000 / VELA1006)随 .Build 走了, 本仓库不再引用 Avalonia - 唯一剩下的跨仓库旋钮是 src/VelaShell.Plugin.Cli 里 VelaShell.PluginSdk 的 PackageReference —— 它管的只是**打包器自己**读清单与 .vpx 容器用的那份契约 VelaToolsVersion 这个属性名保留未改:CI、Set-Version.ps1 与 velashell-docs 的发版流程都按 这个名字对接,改名只是让几处一起动一遍。 验证:dotnet test 44 通过;dotnet pack 出包正常;版本同步体检通过。 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GuPc3rAEeVHYfnicxv4p7y
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
1 participant
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.
VelaShell.PluginSdk.Build决定的是插件作者编译时看到的那份契约,与契约同版本发布才对 —— 所以它搬去了velashell-plugin-sdk。本仓库从此只发vela-plugin一个包。配套 PR:VelaShellLabs/velashell-plugin-sdk#21(那边收下
.Build,并把打包器一并做了进去)。删了什么
src/VelaShell.PluginSdk.Build/velashell-plugin-sdk,在那边用ProjectReference引契约、与契约同版本发布scripts/Invoke-Smoke.ps1+tests/smoke/.Build本仓库现在没有下游
插件工程
dotnet build -t:PackVpx用的不是这个工具:.Build自带一个三条命令的打包器(那边的VelaShell.PluginSdk.Packer)。两边都走VelaShell.PluginSdk里的同一个VpxContainer,包格式一致由类型保证,不靠跨仓库的版本对齐 —— 已实测:那边pack -k签出的包,本仓库的vela-plugin verify读得回来,摘要一致、签名 Valid。所以改
vela-plugin的命令面不会波及任何别的仓库,也没有跨仓库的后续动作要做。vela-plugin的定位收窄成它本来的样子:面向人的完整工具(商店、开发内环、签名、体检)。其它
VELA1000/VELA1006)随.Build走了,本仓库不再引用 Avaloniasrc/VelaShell.Plugin.Cli里VelaShell.PluginSdk的PackageReference—— 它管的只是打包器自己读清单与.vpx容器用的那份契约VelaToolsVersion这个属性名保留未改:CI、Set-Version.ps1与 velashell-docs 的发版流程都按这个名字对接,改名只是让几处一起动一遍验证
dotnet testdotnet packVelaShell.Plugin.Cli.2.0.2.nupkg正常产出velashell-docs 还没动 —— 按 AGENTS.md 的约定那是单独一个 PR。
🤖 Generated with Claude Code
https://claude.ai/code/session_01GuPc3rAEeVHYfnicxv4p7y