chore: 跟上 SDK 2.0.2 的 Avalonia 12.1.2 版本锁,本包发 2.0.2 - #10
Merged
Conversation
宿主升到 Avalonia 12.1.2、velashell-plugin-sdk 把权威的 VelaAvaloniaVersion 抬到 12.1.2 之后,本仓库的两个落点必须同步(否则 VerifyAvaloniaVersionPin 的 VELA1000 / VELA1006 会红): · VelaShell.PluginSdk.Build.csproj 里锁给所有插件工程的精确区间 [12.1.1] → [12.1.2] · build/VelaShell.PluginSdk.Build.props 里随包发下去的 VelaAvaloniaVersion 同时按 zh/sdk/release-process.md §四 第 3 步,把两处 VelaShell.PluginSdk 引用 (.Build 传给插件工程的那份契约,与 vela-plugin 打包器加载的那份,必须同版本) 从 2.0.0 抬到 2.0.2 —— 那正是导出新 $(VelaSdkPinnedAvaloniaVersion) 的那一版。 scripts/Set-Version.ps1 2.0.2 落 VelaToolsVersion(仓库里还停在 1.5.0,而 nuget 上 .Build / vela-plugin 已经是 2.0.1;发版是按标签盖版本号的,这里补齐)。文档横幅在 velashell-docs 的对应 PR 里。⚠️ 合并前提:VelaShell.PluginSdk 2.0.2 已经推上 nuget.org。在那之前本 PR 的 CI 会以 VELA1006 报红(拿到的还是 2.0.0 导出的 12.1.1),这是设计如此的跨仓库核对。 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CbA4MRa7iimxtU99YcZ71f
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.
配套 VelaShellLabs/velashell-plugin-sdk#11(权威
VelaAvaloniaVersion12.1.1 → 12.1.2)。改了什么
src/VelaShell.PluginSdk.Build/VelaShell.PluginSdk.Build.csprojAvalonia[12.1.1][12.1.2]src/VelaShell.PluginSdk.Build/build/VelaShell.PluginSdk.Build.propsVelaAvaloniaVersionsrc/VelaShell.PluginSdk.Build/VelaShell.PluginSdk.Build.csprojVelaShell.PluginSdksrc/VelaShell.Plugin.Cli/VelaShell.Plugin.Cli.csprojVelaShell.PluginSdkDirectory.Build.propsVelaToolsVersionVerifyAvaloniaVersionPin核对的仓库内两个落点(VELA1000);任一不动都会红。VelaShell.PluginSdk引用必须同版本 ——.Build传给插件工程的那份契约,与vela-plugin打包器在插件作者机器上加载的那份,漂了就是同名类型来自两份不同程序集。2.0.2 正是导出新$(VelaSdkPinnedAvaloniaVersion)的那一版(VELA1006)。VelaToolsVersion由pwsh scripts/Set-Version.ps1 2.0.2落。仓库里原本停在 1.5.0,而 nuget.org 上VelaShell.PluginSdk.Build/vela-plugin已经是 2.0.1 —— 发版是按 Release 标签盖版本号的,这次顺手补齐。文档横幅那两处在 velashell-docs 的配套 PR 里。pwsh scripts/Set-Version.ps1 2.0.2 -Check✅VelaShell.PluginSdk2.0.2 必须已经推上 nuget.org。 在那之前本 PR 的 CI 会以 VELA1006 报红 —— 拿到的还是 2.0.0 导出的 12.1.1,而本仓库锁的是 12.1.2。这是设计如此的跨仓库核对,不是回归。顺序:velashell-plugin-sdk#11 合并并发 2.0.2 → 本 PR 变绿 → 合并并发
VelaShell.PluginSdk.Build/vela-plugin2.0.2 → 下游插件仓库的 PR 才能变绿。🤖 Generated with Claude Code
https://claude.ai/code/session_01CbA4MRa7iimxtU99YcZ71f