Skip to content

Packaging: gnustep-packager v0.1.2, and the vendored updater synced from v0.1.1 - #302

Merged
danjboyd merged 5 commits into
mainfrom
packager-v0.1.1
Oct 20, 2026
Merged

danjboyd merged 5 commits into
mainfrom
packager-v0.1.1

Conversation

@danjboyd

Copy link
Copy Markdown
Owner

For 0.3.2. Two commits:

Linux: it builds, with two fewer warnings. The tests pass, 63 suites under both themes (3 skipped under default, 2 under Adwaita).
Still to do: a release-workflow run on the branch (Linux AppImage and Windows MSI), and an update test from 0.3.1 on Windows and Linux. If packager v0.1.2 (#63, relative paths) is tagged first, this moves to v0.1.2.

🤖 Generated with Claude Code

https://claude.ai/code/session_01V8rjzo3Qk8M7WcT9RYfYRW

danjboyd and others added 3 commits October 20, 2026 12:53
The release and Windows preview workflows call the packager's shared
workflow at the v0.1.1 tag instead of main. They no longer pass
packager-repository and packager-ref: with them unset, the workflow checks
out its own commit (gnustep-packager #57). Keeping packager-ref: main
would have run main's scripts under the v0.1.1 workflow.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V8rjzo3Qk8M7WcT9RYfYRW
Picks up, since 44b18e0:
- the update window's progress label is unbezeled (#58);
- a failed install is reported at the next launch, with msiexec's exit
  code in plain words (#37);
- View Changes and Skip This Version can be reached on GNUstep (#50);
- URLs open through ShellExecuteW on Windows. The app already links
  shell32 there;
- two unused symbols are removed, which silences two build warnings.

The local -DHAVE_MODE_T in the three Makefiles is kept.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V8rjzo3Qk8M7WcT9RYfYRW
v0.1.2 adds gnustep-packager #63: a relative path on the command line
(./ScreenshotTool.AppImage Pictures/x.png, or ScreenshotTool.exe docs\x.png
through the MSI launcher) resolves against the caller's directory instead
of the bundle's. Its updater is the same as v0.1.1's, which the vendored
copy is synced from.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V8rjzo3Qk8M7WcT9RYfYRW
@danjboyd danjboyd changed the title Packaging: gnustep-packager v0.1.1, and the vendored updater synced from it Packaging: gnustep-packager v0.1.2, and the vendored updater synced from v0.1.1 Oct 20, 2026
@danjboyd

Copy link
Copy Markdown
Owner Author

Moved to gnustep-packager v0.1.2 (aa1c9ac) in a684f8b. It adds #63: relative command-line paths resolve against the caller's directory. v0.1.2's updater is the same as v0.1.1's, so the vendored sync (d67204f) stands. The preview MSIs already building from d67204f still test the updater. A relative-path launch check (ScreenshotTool.exe docs\x.png, ./ScreenshotTool.AppImage Pictures/x.png) needs a build from this head.

🤖 Generated with Claude Code

GitHub moves ubuntu-latest to Ubuntu 26 from October 2026. The AppImage
is built and its libraries bundled on the packaging runner, so its base
and glibc floor would have changed silently. The packager's AppImage job
(runs-on-appimage), the release's other Linux jobs and the feed redeploy
now name ubuntu-24.04, which build.yml already uses and v0.3.1 was built
on.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V8rjzo3Qk8M7WcT9RYfYRW
@danjboyd

Copy link
Copy Markdown
Owner Author

Windows: GO. I tested CI preview MSIs on Windows 11, using the installed app through its launcher. The update tests used a file:// feed override, with the MSIs served from http://127.0.0.1:8765. Each feed's sha256 matched its MSI.

Test Build Result
Old updater installs the #302 build v0.3.1-rc2 → 0.3.2-rc90 (d67204f), prerelease channel Alert shown, then download, readyToApply, Restart and Install: helper completed, msiexec 0.3.2.90, status 0. Bundle 0.3.2-rc90; relaunched.
#302's updater updates itself 0.3.2-rc90 → 0.3.2-rc91 (d67204f), stable channel The same: msiexec 0.3.2.91, status 0. Bundle 0.3.2-rc91; relaunched.
Relative command-line path (packager v0.1.2, #63) 0.3.2-rc92 (a684f8b) In cmd, from a folder containing docs\x.png: ScreenshotTool.exe docs\x.png opens "x.png - ScreenshotTool". The launcher passes the app the absolute path.

rc90 and rc91 were built from d67204f, before the v0.1.2 pin. As agreed, the updater code they test is the same at a684f8b.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Px6i2CANZszJmJLzAZHoBQ

Both change package-linux in release.yml. #302 drops packager-repository
and packager-ref, and #304 adds runs-on-appimage, which v0.1.2's shared
workflow takes. Resolved here so that #302 merges cleanly after #304.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V8rjzo3Qk8M7WcT9RYfYRW
@danjboyd
danjboyd marked this pull request as ready for review October 20, 2026 21:02
@danjboyd
danjboyd merged commit bc4a06f into main Oct 20, 2026
7 of 8 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