Skip to content

Fix malformed Desktop packaging workflow YAML - #113

Merged
petertzy merged 1 commit into
mainfrom
fix/desktop-packaging-workflow-yaml
Oct 21, 2026
Merged

petertzy merged 1 commit into
mainfrom
fix/desktop-packaging-workflow-yaml

Conversation

@petertzy

Copy link
Copy Markdown
Owner

Restore the manual Desktop packaging workflow after the version calculation edit corrupted its YAML: an unterminated shell command and duplicated job steps made GitHub Actions unable to parse the file.

This change removes the duplicated block and retains manual dispatch, Windows/Linux matrix builds, version manifest creation, and artifact uploads.

The workflow has not yet been run after this fix.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-21T08:27:20.187924Z 635f47e PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@petertzy
petertzy merged commit f7d4e80 into main Oct 21, 2026
4 checks passed

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 635f47e44a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

retention-days: 14
| sort -V | tail -n 1 || true)"
if [[ -z "$version" ]]; then version=v0.1.0; else version="$(awk -F. '{printf "v%d.%d.%d", substr($1,2),$2,$3+1}' <<< "$version")"; fi
version="$(gh release list --repo "$GITHUB_REPOSITORY" --limit 1000 --json tagName --jq '.[].tagName' | grep -E '^v[0-9]+\\.[0-9]+\\.[0-9]+$' | sort -V | tail -n 1 || true)"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Fix doubled escapes in the release-tag regex

When the repository contains a release such as v0.1.0, the single-quoted pattern passes two backslashes before each dot to grep, so it does not match ordinary version tags. Consequently, every packaging run falls back to v0.1.0; after the first release, publish-desktop-release.yml lines 59–61 rejects that already-existing version, preventing subsequent releases. Use a single backslash before each dot in this shell regex.

Useful? React with 👍 / 👎.

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