Skip to content

fix(release): merge duplicate jobs.build.env block in release-tauri.yml#335

Merged
appergb merged 1 commit into
betafrom
fix/release-tauri-duplicate-env-key
May 7, 2026
Merged

fix(release): merge duplicate jobs.build.env block in release-tauri.yml#335
appergb merged 1 commit into
betafrom
fix/release-tauri-duplicate-env-key

Conversation

@appergb
Copy link
Copy Markdown
Collaborator

@appergb appergb commented May 7, 2026

What

PR #330 引入的 release-tauri.yml 在 `jobs.build` 顶层创建了第 2 个 `env:` 块(用来定义 `OPENLESS_RELEASE_CHANNEL`),但 `runs-on` 之后已有一个旧的 `env:` 块(`TAURI_SIGNING_PRIVATE_KEY` 等)。YAML map 不允许重复 key —— GitHub Actions 解析直接 fail。

Why we caught it now

PR-B-1 merge 后 release-tauri.yml 没立刻被跑(它是 tag-triggered)。今天推 `v1.2.24-beta.1-beta-tauri` tag 时第一次执行,立刻 "workflow file issue" 启动失败:run 25501239092

Fix

把 `OPENLESS_RELEASE_CHANNEL` 并入下方唯一的 `env:` 块,注释保留。文件 diff: -8 / +7。

验证

`python -c "yaml.safe_load(...)"` parse 成功,`jobs.build.env` 现在有 3 个 key:`OPENLESS_RELEASE_CHANNEL`、`TAURI_SIGNING_PRIVATE_KEY`、`TAURI_SIGNING_PRIVATE_KEY_PASSWORD`。

Next

合入后删旧 tag `v1.2.24-beta.1-beta-tauri` 并在新 beta HEAD 上重打、重推。

PR #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
@appergb appergb merged commit 2246d8f into beta May 7, 2026
3 checks passed
@appergb appergb deleted the fix/release-tauri-duplicate-env-key branch May 7, 2026 14:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant