feat: productize Windows external-edit learning 还没好#431
Closed
Cooper-X-Oak wants to merge 5 commits into
Closed
Conversation
…ss#333) release-sync: workflow rollout + soaked beta features → main
PR Open-Less#330 在 jobs.build 顶层多加了一个 env: 块来定义 OPENLESS_RELEASE_CHANNEL, 但下面 strategy/runs-on 之后已经有一个 env: 块(TAURI_SIGNING_PRIVATE_KEY 等)。 YAML map 不允许重复 key——GitHub Actions 解析直接 fail,整条 release-tauri.yml 工作流变成 "workflow file issue" 启动失败。 修复:把 OPENLESS_RELEASE_CHANNEL 并到下面那个唯一的 env: 块里,保留完整注释。 校验: - python -c "yaml.safe_load(...)" 解析成功 - jobs.build.env 现在有 3 个 key: OPENLESS_RELEASE_CHANNEL, TAURI_SIGNING_PRIVATE_KEY, TAURI_SIGNING_PRIVATE_KEY_PASSWORD Co-authored-by: baiqing <lbx12309@icloud.com>
包含 PR Open-Less#378 / Open-Less#379 / Open-Less#380 / Open-Less#381 + 版本号 bump。
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.
Summary
old -> newreplacements into formalcorrection-rules.json, and deterministically reuse them on later dictationWhat changed
windows_external_edit.rsand wire it into the formal coordinator dictation lifecyclecorrection-rules.jsonFirst-batch support boundary
Validation
npm run buildcargo build --manifest-path openless-all/app/src-tauri/Cargo.toml --target-dir D:\cargo-targets\openless-extedit --bin openlessSTATUS_ENTRYPOINT_NOT_FOUND, so real smoke/log/rule-file evidence was used for this PRDraft status
This PR should stay draft until:
betapasses