Repository navigation
release: 发布 Cargo 0.1.2 预览版 - #6
Merged
Merged
Conversation
更新 release.yml 中写死的发版说明（原文仍是 0.1.1 的内容），README 从 “未发布源码”改为已发布的预览版，并写明需要 litheLogging 1、暂不收录 Store。
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.
改动
.github/workflows/release.yml：发版说明原来写死的是 0.1.1 的内容（Cargo 路径设置），换成 0.1.2 的变化与兼容性。README.md：“0.1.2 is unreleased preview source / 自行构建” 改为已发布的预览版，从 Releases 下载；写明需要litheLogging: 1、稳定版 0.6.7 无法启动、暂不收录 Lithe Store。plugin.json已在 refactor: use shared executable candidates for Cargo #3 改为 0.1.2，这次不动。0.1.2 包含的功能变化（已合入）
executableResolution: 1）。为什么是预发布、不进 Store
新版 SDK 在宿主不提供
litheLogging时拒绝初始化，而清单无法声明这个依赖，稳定版 v0.6.7 无法提前识别。进 Store 会让稳定版用户升级后插件无法启动。工作流本来就带--prerelease，Store 自动追踪会跳过。验证
node scripts/verify-sdk.mjs、node scripts/test.mjs（0 失败，4 个 Core 集成测试本地跳过，由 CI 运行）、node scripts/package.mjs --expect-tag v0.1.2本地通过。合入后打
v0.1.2tag 触发 Release 工作流。