pkgbuild: Bump grok-bot-bin to 0.39.0 #13

2026-09-04T09:54:58-05:00

eva commented

2026-09-04 09:54:58 -05:00

Why

Scheduled update.yml already detected Cursor Grok Bot 0.39.0 and prepared the bump, but the Actions push to protected master was rejected (pre-receive hook declined). Repo tip is still 0.36.0.

What

PKGBUILD / .SRCINFO bumped to 0.39.0 via ./scripts/update.sh
deb sha256 ae498adaf71f9ff1734a786163c5807fa50165acb5aa102bb68f43ead96de4fe

After merge

Tag v0.39.0 on the merged default tip so build.yml attaches the release asset (same path the scheduled job intended).

Test

./scripts/update.sh no-op after bump (pkgver already 0.39.0)
CI build on tag after cut

## Why Scheduled `update.yml` already detected Cursor Grok Bot **0.39.0** and prepared the bump, but the Actions push to protected `master` was rejected (`pre-receive hook declined`). Repo tip is still **0.36.0**. ## What - `PKGBUILD` / `.SRCINFO` bumped to **0.39.0** via `./scripts/update.sh` - deb sha256 `ae498adaf71f9ff1734a786163c5807fa50165acb5aa102bb68f43ead96de4fe` ## After merge Tag `v0.39.0` on the merged default tip so `build.yml` attaches the release asset (same path the scheduled job intended). ## Test - `./scripts/update.sh` no-op after bump (pkgver already 0.39.0) - CI build on tag after cut

eva added 1 commit 2026-09-04 09:54:58 -05:00

pkgbuild: Bump grok-bot-bin to 0.39.0 eb83529a0d

eva merged commit 049b00de10 into master

2026-09-04 09:55:15 -05:00

eva referenced this pull request

2026-09-04 09:56:51 -05:00

ci: Make update.yml open a PR when master push is blocked #14

ash referenced this pull request

2026-09-04 10:41:29 -05:00

ci: Open bump PRs instead of pushing protected master #15

Sign in to join this conversation.