Repository navigation
Automate Grok Bot releases - #583
Conversation
|
This is my first package contribution, so the native x86_64/aarch64 build matrix is waiting on the repository trust gate. Please apply |
|
Hi — just a polite bump from an Omarchy user still on pacman 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 |
|
@ryanrhughes Thanks for the |
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.
|
@ryanrhughes thanks again for the |
|
should grok-bot be included in mise updates instead to make it like codex and grok, so it can be updated faster? |
|
Thanks for this. I checked Cursor's apt indexes just now, and both amd64 and arm64 are on 0.68.1:
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 Happy to recheck the indexes if a newer build appears. I will leave the branch with you. |
|
Thanks for checking the indexes. The goal here is to bring grok-bot into Omarchy's normal update process. This PR removes On the updater: you're right that 0.68.1's in-app updater covers Linux. For this package, the install under |
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.
Publish succeeded → livePackages: grok-bot (x86_64, PR artifact); grok-bot (aarch64, PR artifact)
|
Summary
omarchy-update/ pacman) like the other packages/opt/Grok Botupdates through pacman, not the app's in-app updatergrok-botfrom the "Existing manual holds" list indocs/upstream-sources.md, since it now syncs automatically (from grok-bot: track stable releases and update to 0.68.1 #848, thanks @h-kairalla)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: falsestill excludes Grok Bot from the six-hour workflow, whileupdate-pkgver.shexpects the old commit-bearing Darwin feed andGrok_Bot_<version>.debfilename. Unlike the earlier attempt in #364, this preserves the merged ARM packaging and AUR attribution.Cursor's
amd64andarm64package 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.shpkgbuilds/grok-bot/.omarchy/upstream.shreturns 0.68.1 and the published checksums for both architectures (matchingsha256sumof both downloaded debs), and fails with a clear message when theFilename:path is altered./bin/sync-upstream grok-botreports the recipe current at 0.68.1makepkg --printsrcinfoshows 0.68.1 with the pool URLs and checksums for both architectures./bin/sync-upstream self-testpassesbin/build --mirror edge --arch x86_64 --package grok-botbuilds successfully (run on an earlier version; package CI covers 0.68.1)git diff --checkpassesThe 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-approvedlabel before package CI runs.