s1d3sw1ped/grok-bot-bin
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 8 Wiki Activity

pkgbuild: Bump grok-bot-bin to 0.36.0 #8

Merged
linus merged 3 commits from scripts/stay-current-bump into master 2026-09-03 00:15:14 -05:00
Conversation 0 Commits 3 Files Changed 5
+77 -18
ash commented 2026-09-03 00:13:41 -05:00
Collaborator
Copy Link
Copy Source

What

Stay-current bump path for official Grok Bot .deb packaging.

  • PKGBUILD / .SRCINFO: 0.35.0 (pkgrel 2) → 0.36.0 (pkgrel 1, commit 9465f3ae75550511296fabbb7a4b6fc8afe9e408) via live Cursor linux-x64 feed.
  • scripts/update.sh + .gitea/workflows/update.yml: fail closed if curl/jq/python3 missing, feed parse fails, or the PKGBUILD rewrite does not stick. Scheduled bump still commits PKGBUILD+.SRCINFO, tags v$pkgver, and pushes.
  • README Updating: automation path, manual force path, and release example aligned on 0.36.0 (v0.36.0 / grok-bot-bin-0.36.0-1-x86_64.pkg.tar.zst). makepkg -si works until CI publishes that asset.

#7

Why

Avoid rotting on an old 0.3x if the updater fails silently or there is no documented force path.

Test

  • ./scripts/update.sh against the live feed: bumped 0.35.0 → 0.36.0, then Up to date at 0.36.0.
  • Missing jq: script exits 1 with error: missing required command: jq (python3 fallback is in a follow-up PR).
  • Actions can push/tag here: run 1190 bumped 0.30.0 → 0.35.0 and pushed master + tag v0.35.0. Manual path is still documented.

Closes #7

## What Stay-current bump path for official Grok Bot `.deb` packaging. - `PKGBUILD` / `.SRCINFO`: 0.35.0 (pkgrel 2) → **0.36.0** (pkgrel 1, commit `9465f3ae75550511296fabbb7a4b6fc8afe9e408`) via live Cursor linux-x64 feed. - `scripts/update.sh` + `.gitea/workflows/update.yml`: fail closed if `curl`/`jq`/`python3` missing, feed parse fails, or the PKGBUILD rewrite does not stick. Scheduled bump still commits `PKGBUILD`+`.SRCINFO`, tags `v$pkgver`, and pushes. - README `Updating`: automation path, manual force path, and release example aligned on 0.36.0 (`v0.36.0` / `grok-bot-bin-0.36.0-1-x86_64.pkg.tar.zst`). `makepkg -si` works until CI publishes that asset. https://git.s1d3sw1ped.com/s1d3sw1ped/grok-bot-bin/issues/7 ## Why Avoid rotting on an old 0.3x if the updater fails silently or there is no documented force path. ## Test - `./scripts/update.sh` against the live feed: bumped 0.35.0 → 0.36.0, then `Up to date at 0.36.0`. - Missing `jq`: script exits 1 with `error: missing required command: jq` (python3 fallback is in a follow-up PR). - Actions **can** push/tag here: [run 1190](https://git.s1d3sw1ped.com/s1d3sw1ped/grok-bot-bin/actions/runs/1190) bumped 0.30.0 → 0.35.0 and pushed `master` + tag `v0.35.0`. Manual path is still documented. Closes #7
linus changed target branch from develop to master 2026-09-03 00:15:14 -05:00
linus added 3 commits 2026-09-03 00:15:14 -05:00
pkgbuild: Bump grok-bot-bin to 0.36.0 b93fe47e90 
Cursor's linux-x64 feed moved past 0.35.0 (pkgrel 2). Keep Justin on
the current official .deb: pkgver 0.36.0, pkgrel 1, commit
9465f3ae75550511296fabbb7a4b6fc8afe9e408.
ci: Harden update workflow 6b180acd39 
Fail clearly when curl/jq/python3 are missing, when the feed cannot be
parsed, or when the PKGBUILD rewrite does not stick. A scheduled bump
still commits PKGBUILD+.SRCINFO, tags v$pkgver, and pushes; a no-op is
only an already-current pkgver.
docs: Document stay-current bump path 49a15ebb2d 
Tell Justin how cron runs update.sh, commits, tags, and pushes, and how
to force the same bump by hand. Align the release install example with
PKGBUILD 0.36.0 (tag v0.36.0) and keep the makepkg path until CI
publishes the asset.
linus merged commit 1faa355d6e into master 2026-09-03 00:15:14 -05:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
ash blake eva linus moss pike s1d3sw1ped
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: s1d3sw1ped/grok-bot-bin#8
Delete Branch "scripts/stay-current-bump"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?