Skip to content

Automate Grok Bot releases - #583

Merged
ryanrhughes merged 3 commits into
omacom:masterfrom
timothygwright:grok-bot-upstream-sync
Oct 8, 2026
Merged

ryanrhughes merged 3 commits into
omacom:masterfrom
timothygwright:grok-bot-upstream-sync

Conversation

@timothygwright

@timothygwright timothygwright commented Sep 21, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • update Grok Bot from 0.47.0 to 0.68.1 for x86_64 and aarch64 (a starting point; the scheduled sync moves it forward after merge)
  • source immutable packages from Cursor's official Debian pool
  • track both architecture indexes through the scheduled upstream sync, so Grok Bot updates through the normal Omarchy process (omarchy-update / pacman) like the other packages
  • wait for both architectures to publish the same version before updating
  • put this desktop app on the fast release ring; the packaged install under /opt/Grok Bot updates through pacman, not the app's in-app updater
  • remove the obsolete commit-based manual updater
  • drop grok-bot from the "Existing manual holds" list in docs/upstream-sources.md, since it now syncs automatically (from grok-bot: track stable releases and update to 0.68.1 #848, thanks @h-kairalla)
  • check that the newest index stanza's Filename: is the versioned pool path (pool/grok-bot/g/gr/grok-bot_<version>_<debarch>.deb) the PKGBUILD downloads from, and fail loudly otherwise (also from grok-bot: track stable releases and update to 0.68.1 #848)

This follows up on #339 against the current dual-architecture recipe. The existing sync: false still excludes Grok Bot from the six-hour workflow, while update-pkgver.sh expects the old commit-bearing Darwin feed and Grok_Bot_<version>.deb filename. Unlike the earlier attempt in #364, this preserves the merged ARM packaging and AUR attribution.

Cursor's amd64 and arm64 package indexes now provide version and SHA256 metadata directly, so routine checks require only two small requests and do not download either package. The apt pool retains the versioned artifacts used by the PKGBUILD.

Closes #339

Verification

  • bash -n pkgbuilds/grok-bot/.omarchy/upstream.sh
  • pkgbuilds/grok-bot/.omarchy/upstream.sh returns 0.68.1 and the published checksums for both architectures (matching sha256sum of both downloaded debs), and fails with a clear message when the Filename: path is altered
  • ./bin/sync-upstream grok-bot reports the recipe current at 0.68.1
  • makepkg --printsrcinfo shows 0.68.1 with the pool URLs and checksums for both architectures
  • ./bin/sync-upstream self-test passes
  • bin/build --mirror edge --arch x86_64 --package grok-bot builds successfully (run on an earlier version; package CI covers 0.68.1)
  • git diff --check passes

The aarch64 package build is left to the repository's native gated builder. This contributor is not yet vouched, so the PR will need the build-approved label before package CI runs.

@timothygwright

Copy link
Copy Markdown
Contributor Author

This is my first package contribution, so the native x86_64/aarch64 build matrix is waiting on the repository trust gate. Please apply build-approved when ready to run it; the x86_64 package has already built successfully locally with bin/build --mirror edge --arch x86_64 --package grok-bot.

@Loafer19

Copy link
Copy Markdown

Hi — just a polite bump from an Omarchy user still on pacman grok-bot 0.47.0 while Cursor’s apt index is already 0.61.0 (and this PR targets 0.57.1, which would still help a lot).

Linux has no in-app updater, so the Omarchy package is the update path for many of us. Looks like this is waiting on the build-approved label / trust gate for the dual-arch CI. Happy to test an edge build once it lands. Thanks for the work on automating this.

@ryanrhughes ryanrhughes added build-approved Maintainer approved this PR to build on the self-hosted pool and removed build-approved Maintainer approved this PR to build on the self-hosted pool labels Sep 28, 2026

Copy link
Copy Markdown
Contributor Author

@ryanrhughes Thanks for the build-approved label — dual-arch CI came back green on both x86_64 and aarch64. When you have a minute, would you mind merging this? Users are still on pacman grok-bot 0.47.0 while apt has moved further ahead. Appreciate it.

Bump both architectures to Cursor apt 0.66.0 with matching SHA256s,
introduce a versioned _pool URL helper, and filter Packages stanzas by
Package: grok-bot so sync stays correct if the index grows.
@timothygwright

Copy link
Copy Markdown
Contributor Author

@ryanrhughes thanks again for the build-approved label on #583 — dual-arch CI was green after that. I’ve refreshed the tip to Cursor’s current apt grok-bot 0.66.0 for both amd64 and arm64 (checksums from the Packages indexes, pool URLs, same-version gate, fast ring, Darwin/_commit updater still gone). Ready to merge whenever you have a moment; happy to defer or close in favor of #725/#744/#757 if you’d rather land one of those instead.

@ewinnington

Copy link
Copy Markdown

should grok-bot be included in mise updates instead to make it like codex and grok, so it can be updated faster?

@badenpiland

Copy link
Copy Markdown

Thanks for this. I checked Cursor's apt indexes just now, and both amd64 and arm64 are on 0.68.1:

  • amd64 b2be8106d2b3eae07d983d5f1ca77b657accde666dc440db2a409421ecff3359
  • arm64 3f85fbe2ba3c1d122aa16f8be672076bc19146e07e9d431f37a93b85fa75a93f

I had seen 0.61.0 earlier in the thread, so I wanted to pass the current numbers along. The branch looks pinned at 0.66.0.

I was also curious about the "non-self-updating" note in the summary. In 0.68.1 the in-app updater does include Linux, though an install under /opt/Grok Bot is still described as updating through the system package manager. I am not sure it will update a packaged install on its own. I noticed #755 talking about later package bumps landing by themselves for the other desktop apps, in case that is relevant. No expectation either way.

Happy to recheck the indexes if a newer build appears. I will leave the branch with you.

Copy link
Copy Markdown
Contributor Author

Thanks for checking the indexes. The goal here is to bring grok-bot into Omarchy's normal update process. This PR removes sync: false, so the scheduled upstream sync tracks Cursor's amd64 and arm64 apt indexes and bumps the package once both architectures publish the same version. After it merges, 0.68.1 and anything newer should land automatically through omarchy-update, with no hand pins. The 0.66.0 in the branch is just a starting point.

On the updater: you're right that 0.68.1's in-app updater covers Linux. For this package, the install under /opt/Grok Bot is meant to update through pacman like the other Omarchy desktop apps, which is what I meant by "non-self-updating". I'll reword the summary to make that clearer. Thanks for flagging #755 too.

Bump both architectures to Cursor apt 0.68.1 with the SHA256s from the
amd64/arm64 Packages indexes (verified against the downloaded debs).

Drop grok-bot from the manual holds list in docs/upstream-sources.md and
have upstream.sh check that the newest stanza's Filename is the versioned
pool path the PKGBUILD downloads from. Both additions come from omacom#848.
@ryanrhughes
ryanrhughes merged commit cb3909f into omacom:master Oct 8, 2026
7 checks passed
@github-actions

github-actions Bot commented Oct 8, 2026

Copy link
Copy Markdown
Contributor

Publish succeeded → live

Packages: grok-bot (x86_64, PR artifact); grok-bot (aarch64, PR artifact)

  • edge/x86_64: grok-bot-0.68.1-1-x86_64
  • edge/aarch64: grok-bot-0.68.1-1-aarch64
  • rc/x86_64: grok-bot-0.68.1-1-x86_64
  • rc/aarch64: grok-bot-0.68.1-1-aarch64
  • stable/x86_64: grok-bot-0.68.1-1-x86_64
  • stable/aarch64: grok-bot-0.68.1-1-aarch64

Commit cb3909f · run

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build-approved Maintainer approved this PR to build on the self-hosted pool

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Put grok-bot on the fast release ring and wire sync-upstream

5 participants