Files
BillyOutlastandClaude Opus 5.5 9ceb42e62d Release: the update feed survived in the built artifact — set publish: null
The artifact from the green Linux run still contains
resources/app-update.yml (provider github, owner 4ian, repo GDevelop).
Deleting the `publish` key is not enough: with no publish config,
electron-builder 26 (PublishManager.getPublishConfigsForUpdateInfo)
derives the feed from package.json `repository` and writes the file
anyway. Only an explicit `publish: null` disables that.

On the Linux zip it happened to be inert (electron-updater needs an
AppImage there). On Windows NSIS and macOS it would be a live feed that
replaces the patched app with stock GDevelop on the next upstream
release — the opposite of the release notes' claim.

The script now replaces the block with `publish: null`, evaluates the
config to prove it, and refuses a config with no publish key at all
(previously accepted as 'already neutered', which is exactly the
auto-detect case).

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-10-11 15:51:06 -04:00

5 lines
206 B
Plaintext

# Patches, launcher files and the hash-pinned Tier-2 runtime must stay
# byte-exact on every platform: a CRLF checkout breaks every hunk and
# every sha256 pin. No end-of-line conversion, anywhere.
* -text