[codex] Sync qwen-code desktop release updates#29
Merged
Conversation
…(#3778) OpenWork-Sync-Mode: export Qwen-Code-Base: ac4d100e1af971c3b5e2530427cc9c5278a99b74 Qwen-Code-Commit: 62e45c567fe18b9387ca1a18737e64ef6e1c2c00 OpenWork-Base: 44c061d
OpenWork-Sync-Mode: export Qwen-Code-Base: 5121c6563ef78b9b3bad606324ffde89292a5d84 Qwen-Code-Commit: 04412163ab16875d0009a06491f7e14217843c35 OpenWork-Base: 10f3bf6
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.
Summary
Sync the latest qwen-code desktop changes into OpenWork while preserving OpenWork-owned repository content.
This brings over the desktop pet and security document formatting updates produced by the qwen-code desktop package sync, and aligns the Windows release channel with the current qwen-code policy for unsigned Windows artifacts.
Why
OpenWork's desktop release flow already allows publishing Windows artifacts without signing credentials in draft and dry-run scenarios. The Windows updater configuration also needs to match that policy from the first release so unsigned Windows builds can keep receiving updates without code-signature verification blocking the channel.
Validation
git diff --check HEADsuccessfully.