Repository navigation
G9 3.1.1
Download
| System | File | Updates |
|---|---|---|
| Windows 10/11 (x64) | G9-Setup-3.1.1.exe — per user, no administrator rights |
Automatic: G9 checks these releases, downloads in the background and asks before installing |
| macOS 12+ (Apple silicon) | G9-3.1.1-mac-arm64.dmg |
G9 tells you when a release is out; download it and replace the app (the app is not signed with an Apple Developer ID yet, so macOS cannot install updates into it) |
| macOS 12+ (Intel) | G9-3.1.1-mac-x64.dmg |
As above |
| Linux (x64) | G9-x86_64.AppImage — keep this file name: updates replace the file in place |
Automatic, like Windows |
| Debian/Ubuntu (x64) | G9_3.1.1_amd64.deb |
G9 tells you; install the new .deb with your package manager |
The installers are not code-signed: Windows SmartScreen and macOS Gatekeeper ask once before the first start. See the README for what to click, and for the browser extension (loaded once, updated by G9 itself).
latest.yml, latest-mac.yml and latest-linux.yml are the update metadata G9 reads; the .zip and .blockmap files are for the updater.
What changed in 3.1.1
Why. 3.1.0 is the first release on GitHub. Two things could only be done after it existed: the
update test against the real feed, and README pictures whose update status is true.
The update from GitHub, end to end (desktop/test/update-e2e.mjs --feed official, real
packages, no settings written): an older build of the 3.1.0 source (3.0.999), freshly installed,
checked github.com/ImanKari/G9BrowserAgent by itself, downloaded the published 3.1.0 from GitHub's
storage (SHA-512 from the release's latest*.yml), installed it and restarted as 3.1.0.
Windows 11, the owner's workstation: 6 of 6 (the extension in Chrome 153 connected before the
update). Linux AppImage, a clean Ubuntu container: 6 of 6 (the published G9-x86_64.AppImage
replaced the installed file byte for byte; Chrome could not be downloaded into the container that
time, so the extension half ran only in the pipeline's local-feed test, 20 of 20 with Edge). Found on
the way: Node on the owner's workstation cannot reach api.github.com (a network timeout; git,
Docker and the app itself can), which is why the check goes through the app, as a person's would.
The pictures. Made again from the 3.1.1 source in the neutral container: the footer and
Settings → Updates now read "up to date (3.1.1)" — a real check against the published releases —
instead of "no G9 release is published yet", and the Engines view shows the launched tabs' titles
(the 3.1.0 fix). The README and README.fa gained the Updates picture.
No runtime behaviour changed. Version 3.1.1 in package.json, extension/manifest.json,
desktop/package.json and desktop/package-lock.json.
SHA-256
492147ca36f7202ec03a4b33c052e48cf1466dc276c0f0a44ce2a95ef3457d5a G9-3.1.1-mac-arm64.dmg
22f044722d548ea8bf2d372d6b30671fa9e1861d5b260743f289f0123b607d01 G9-3.1.1-mac-arm64.dmg.blockmap
adeb1f76b2a7aa6019910a62f78a3a5e19290e4af94cab5915bcf8bdec3af229 G9-3.1.1-mac-arm64.zip
439e364ed3ab3239812e6e255c8a1224418cedce0abbdae9a73bf301b5e780aa G9-3.1.1-mac-arm64.zip.blockmap
83f5b5770953c78ffaca58978700375d510871700485905f725054d004cb7246 G9-3.1.1-mac-x64.dmg
920ca09d0795197088994b75143aaf3a9cdde0c6e861de4f9bc19c768886c58b G9-3.1.1-mac-x64.dmg.blockmap
a7968b4870bc4aba75686782a4fdfd581f9f7d1840a8f63e0c76a53e40abf998 G9-3.1.1-mac-x64.zip
88ad38c8c5d844d553e1c81c3b35caa633e7c7609085859837c0c9a258ea3fd0 G9-3.1.1-mac-x64.zip.blockmap
e5817af7401c512c8f18f673435726bccd5e2de597275399f4503798acc30559 G9-Setup-3.1.1.exe
f21220247d7d8ed6d082e134fd08a9964f27e8e6ed85454f939339f0514e4238 G9-Setup-3.1.1.exe.blockmap
d47c5992e723ad12fb23e1550b8a5d855b2d15323ffe3440169f30774b63fc04 G9-x86_64.AppImage
2ce9cb9713e179bd9ae622120c86a5c43777a0eb2baaf0216a00c23cae29aeef G9_3.1.1_amd64.deb