Skip to content

GSO-1 v0.1.1

Choose a tag to compare

View all tags
@github-actions github-actions released this 26 Aug 01:46
· 6 commits to main since this release
v0.1.1
d4d2792

Install

Platform File
macOS (Apple Silicon) GSO-1-0.1.1-arm64.dmg
macOS (Intel) GSO-1-0.1.1.dmg
Windows GSO-1.Setup.0.1.1.exe
Linux GSO-1-0.1.1-x86_64.AppImage / GSO-1-0.1.1-amd64.deb

On first run GSO-1 asks which folder holds your projects. That is the whole
setup: no Python, no terminal, no config file. Verify a download against
SHA256SUMS.txt.

macOS 15 and later: approve it once in Settings

These builds are signed ad-hoc rather than with a paid Apple Developer ID, so
the first launch is blocked with "Apple could not verify GSO-1 is free of
malware that may harm your Mac."

Right-click and Open no longer works on macOS 15+ and that dialog offers
only Done and Move to Bin. Neither is the answer.

  1. Drag GSO-1 into Applications, try to open it once, then click Done.

  2. Open System Settings → Privacy & Security.

  3. Scroll to the Security section near the bottom. You will see:

    "GSO-1" was blocked to protect your Mac. [Open Anyway]

  4. Click Open Anyway, authenticate with Touch ID or your password, then
    click Open in the confirmation.

That is Apple's sanctioned route and it only happens once. If the button is not
there it has expired: try opening GSO-1 again to make it reappear.

Prefer the terminal? xattr -dr com.apple.quarantine /Applications/GSO-1.app
removes the quarantine flag your browser attached. Check the download against
SHA256SUMS.txt first.

Windows

SmartScreen needs "More info" then "Run anyway".

What changed in 0.1.1

Both fixes were found by installing the v0.1.0 build and running it, which is
the only test that would have caught either.

  • macOS builds reported themselves as damaged. electron-builder copies the
    frozen backend in after Electron's own signature is applied, invalidating it,
    and nothing put it back. An invalid signature is worse than none: macOS
    refuses the app outright instead of offering the approval flow above. Builds
    are now ad-hoc signed after packing, and the build fails if the signature does
    not validate.
  • Application state was written into Electron's browser profile. The
    registry, event log and job state sat interleaved with Chromium's cookies,
    caches and lock files. State now lives in a data subdirectory.

Full changelog: https://github.com/rafsunsheikh/gso-1/blob/main/CHANGELOG.md

Assets 8
Loading