Skip to content

release: write per-platform update manifest fragments with sha256 and size - #241

Closed
rodgolpe wants to merge 2 commits into
feat/5.7-updater-applyfrom
feat/5.7-updater-manifest
Closed

release: write per-platform update manifest fragments with sha256 and size#241
rodgolpe wants to merge 2 commits into
feat/5.7-updater-applyfrom
feat/5.7-updater-manifest

Conversation

@rodgolpe

Copy link
Copy Markdown
Contributor

After each OS artifact, hash it, write releases/update-manifest.d/.json, and merge same-version fragments into releases/manifest.json. Packaged package.json honors ONLYKEY_UPDATE_MANIFEST_URL and ONLYKEY_UPDATE_BASE_URL. Does not upload to S3.

… size

After each OS artifact, hash it, write releases/update-manifest.d/<key>.json, and merge same-version fragments into releases/manifest.json. Packaged package.json honors ONLYKEY_UPDATE_MANIFEST_URL and ONLYKEY_UPDATE_BASE_URL. Does not upload to S3.
Authenticode/notarization changes bytes, so npm run release no longer writes the update manifest. After signing in place, npm run update-manifest hashes that file, refuses NotSigned on Windows/macOS, and reminds the operator to upload the same signed artifact.
@rodgolpe

Copy link
Copy Markdown
Contributor Author

@rodgolpe rodgolpe closed this Sep 12, 2026
@rodgolpe
rodgolpe deleted the feat/5.7-updater-manifest branch September 12, 2026 03:35
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