grok-bot: bump 0.29.0 → 0.47.0 (upstream renamed the Linux .deb) - #401
Open
patrickpassosb wants to merge 1 commit into
Open
patrickpassosb wants to merge 1 commit into
patrickpassosb wants to merge 1 commit into
Conversation
- Upstream renamed the Linux .deb to gro-bot_amd64.deb and moved it under a new commit path on downloads.cursor.com. - Verified: source URL fetches, sha256 matches the official artifact, makepkg builds, wrapper/sand symlink/desktop/setuid sandbox all land. - Note: update-pkgver.sh's commit extraction now fails — Cursor's update feed URL no longer embeds a 40-char commit hash. The current commit path must be taken from the cursor.com download page instead.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
pkgbuilds/grok-botis pinned to 0.29.0 while upstream stable is 0.47.0 (confirmed via Cursor's update feed today). Users installing Grok Bot from Omarchy's launcher get a 3-releases-old app with no upgrade path —omarchy-pkg-add grok-botkeeps serving 0.29.0 frompkgs.omarchy.org.Precedent: omacom/omarchy#8070 (same failure class at 0.18.0, fixed by PR #201 in this repo).
What changed upstream
Two things besides the version bump broke the PKGBUILD as-is:
grok-bot_0.47.0_amd64.deb(wasGrok_Bot_<ver>.deb).https://downloads.cursor.com/grokbot/stable/<40-char-commit>/linux/x64/.... The current commit path isc1e7d7a46549956d25f53e9c0b9f59666e03aa3a(from the official download page at cursor.com/download/bot).This PR bumps
pkgver,_commit, the source filename, and the sha256.Also stale:
update-pkgver.shThe script extracts the commit hash from the update feed URL with a
[0-9a-f]{40}regex — but the feed URL (https://api2.cursor.sh/updates/api/update/darwin-arm64/sand/0.0.0/.../stable) no longer embeds a 40-char commit (verified today; it resolves to/grokbot/stable/darwin-arm64/0.47.0/...). Running it now fails to resolve a commit, which is likely how the pin silently aged. The commit path now has to be scraped from the download page (or the feed format re-checked). I left the script untouched to keep this PR a clean bump — happy to follow up with a fix if you want it.Verification
makepkgwith this exact PKGBUILD buildsgrok-bot-0.47.0-1-x86_64.pkg.tar.zst(no dpkg needed; bsdtar path works)usr/bin/grok-bot, thesandsymlink, the desktop entry, and the setuidchrome-sandbox.debfetches (HTTP 200) from the pinned URL and its sha256 matches (11ca0f51a535b97af51a352adf9c0f9ecd2e1b0430a69ae9451b688a7a065808)Filed by an AI coding agent (Pi harness, model not self-reported) on behalf of patrickpassosb.