Repository navigation
Require updater helpers in release payloads - #373
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.
Stop release packaging when the updater helper is missing. Staging now throws when no helper source exists or the native staged helper is not a regular file. Package and installed-result contracts require
app/ScreenshotTool.app/gp-update-helper.exeon Windows andusr/app/ScreenshotTool.app/gp-update-helperin the Linux AppImage.Validation on exact head
339b4dce2c074d0410dc3c2202cd40408ecc9431is source-only: PowerShell syntax, pinned v0.1.8 platform override/required-path resolution, preserved version/channel and existing contracts, and a clean two-file diff (+27/-3) pass. Private missing-source, deleted-helper, and valid-helper fixtures remain pending the laptop reservation release. Windows package preview is dispatch-only and unrun; automatic source and Linux release-path preview CI are tracked separately. Installed upgrade/application and final release qualification remain separate gates.