Fix release packaging - #2
Merged
Merged
Conversation
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
Fixes the first post-merge Release workflow failure and completes the release package metadata.
package.jsonvalid on Windows..debpackaging does not require an author email.Root cause
The release workflow wrote the two literal characters
\\nafterpackage.json, which made Windows E2E fail to parse it. Linux packaging then failed because Electron Builder requires either an author email or an explicit Debian maintainer.Validation
npm run typechecknpm run prepare:codex && npm run package:linux -- --publish never.debcontainsresources/notices/LICENSEandresources/notices/PRIVACY.md.The Windows path is covered by the PR CI matrix; the change removes the shell-escaping ambiguity that caused its prior JSON parse failure.