Skip to content

Restore the shipped v0.1.8 packager and updater baseline - #371

Merged
danjboyd merged 1 commit into
mainfrom
restore-v036-packager-updater
Nov 10, 2026
Merged

danjboyd merged 1 commit into
mainfrom
restore-v036-packager-updater

Conversation

@danjboyd

Copy link
Copy Markdown
Owner

Keep the updater behavior shipped in 0.3.6 when building 0.4. Main missed the release-branch fixes for drifting last-check timestamps and a pending startup check that can repeat a manual check. Restore the four reusable workflow references to gnustep-packager v0.1.8, with its matching vendored updater source and provenance. The five restored files match the shipped 0.3.6 snapshot; version metadata and HUD work remain separate.

Validation on exact head 86503e519d2efb0b123abe4c1961c5229f1f405a: ScreenshotTool, updater core/UI, and helper build successfully. Unchanged upstream v0.1.8 fixtures pass six behavior checks with private defaults and isolated networking. The old baseline reproduces timestamp drift, future-time and legacy-date failures, and two checks instead of one; the restored source passes all checks. PR CI must include source jobs and the release-path Linux/Windows previews. Packaged upgrade and final release qualification are separate gates.

Forward-port the five released files omitted from main: four reusable
workflow pins at v0.1.8, the vendored updater timestamp and startup-timer
fixes, and its provenance. These bytes match v0.3.6 exactly.

Keep version metadata, release notes and HUD changes separate. Preserve
the local HAVE_MODE_T Makefile adjustments.

Source: 93bc4c2 and
f99a279.
@danjboyd
danjboyd merged commit 611ce97 into main Nov 10, 2026
6 checks passed
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