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

Stay-current: reliable bump path when upstream Grok Bot .deb moves #7

New Issue
Closed
opened 2026-09-03 00:04:05 -05:00 by linus · 1 comment
linus commented 2026-09-03 00:04:05 -05:00
Collaborator
Copy Link
Copy Source

Problem

Packaging goal stays CachyOS/Arch install of official Grok Bot. scripts/update.sh + scheduled .gitea/workflows/update.yml exist, but the product risk is rot after a bump (stuck on an old 0.3x) if the path fails silently or docs don’t tell Justin how to force a stay-current update.

Goal

Stay-current for the same packaging product — when Cursor’s linux-x64 feed moves, this repo can bump and Justin can install/update without archaeology.

Scope (do)

  • Prove / harden the bump path: scripts/update.sh against the live feed; scheduled workflow still the intended automation.
  • Fix any concrete gap that leaves PKGBUILD/README/release story lying (version claims, update instructions, failed silent no-op).
  • Prefer minimal diff: delete dead update instructions; don’t add a second updater.

Out of scope

  • Rewriting the Electron app, AUR submission campaigns, new package formats, security sandbox redesign (Blake if that surfaces).

Acceptance

  1. Documented stay-current path: how automation bumps, and how a human forces ./scripts/update.sh + rebuild when needed.
  2. After a dry run (or real bump if feed is ahead), README/PKGBUILD/Updating section agree on current version story.
  3. If Actions can’t push/tag in this forge setup, say so in README and leave a working manual path — don’t pretend the cron works.

Docs bar

README Updating (and any release install examples with pinned versions) updated in the same PR as packaging/script changes.

Owner

@ash — wait for this issue; one PR.

## Problem Packaging goal stays CachyOS/Arch install of official Grok Bot. `scripts/update.sh` + scheduled `.gitea/workflows/update.yml` exist, but the product risk is rot after a bump (stuck on an old 0.3x) if the path fails silently or docs don’t tell Justin how to force a stay-current update. ## Goal Stay-current for the same packaging product — when Cursor’s linux-x64 feed moves, this repo can bump and Justin can install/update without archaeology. ## Scope (do) - Prove / harden the bump path: `scripts/update.sh` against the live feed; scheduled workflow still the intended automation. - Fix any concrete gap that leaves PKGBUILD/README/release story lying (version claims, update instructions, failed silent no-op). - Prefer minimal diff: delete dead update instructions; don’t add a second updater. ## Out of scope - Rewriting the Electron app, AUR submission campaigns, new package formats, security sandbox redesign (Blake if that surfaces). ## Acceptance 1. Documented stay-current path: how automation bumps, and how a human forces `./scripts/update.sh` + rebuild when needed. 2. After a dry run (or real bump if feed is ahead), README/PKGBUILD/`Updating` section agree on current version story. 3. If Actions can’t push/tag in this forge setup, say so in README and leave a working manual path — don’t pretend the cron works. ## Docs bar README `Updating` (and any release install examples with pinned versions) updated in the **same PR** as packaging/script changes. ## Owner @ash — wait for this issue; one PR.
ash commented 2026-09-03 00:13:51 -05:00
Collaborator
Copy Link
Copy Source

Acceptance evidence for stay-current (#7):

  • Feed bump: ./scripts/update.sh against the live Cursor linux-x64 feed rewrote PKGBUILD/.SRCINFO 0.35.0 (pkgrel 2) → 0.36.0 (pkgrel 1, commit 9465f3ae75550511296fabbb7a4b6fc8afe9e408). Re-run after that: Up to date at 0.36.0.
  • Actions push/tag works: run 1190 (schedule on master) bumped 0.30.0 → 0.35.0 and pushed master + tag v0.35.0. Cron is not documented as unable to push.
  • README Updating: documents scheduled .gitea/workflows/update.yml (run ./scripts/update.sh, commit, tag v$pkgver, push; tag triggers build/release) and the human force path (./scripts/update.sh then commit/tag/push or PR on develop + makepkg -si / Releases). Release example is v0.36.0 / grok-bot-bin-0.36.0-1-x86_64.pkg.tar.zst; until CI publishes that asset, makepkg -si works. PKGBUILD/README agree on 0.36.0.
  • PR (not merged): #8 (HEAD 49a15ebb2d1473666b7faed4a464a69c25eb64b5)
Acceptance evidence for stay-current (#7): - **Feed bump:** `./scripts/update.sh` against the live Cursor linux-x64 feed rewrote `PKGBUILD`/`.SRCINFO` **0.35.0 (pkgrel 2) → 0.36.0 (pkgrel 1, commit 9465f3ae75550511296fabbb7a4b6fc8afe9e408)**. Re-run after that: `Up to date at 0.36.0`. - **Actions push/tag works:** [run 1190](https://git.s1d3sw1ped.com/s1d3sw1ped/grok-bot-bin/actions/runs/1190) (schedule on `master`) bumped 0.30.0 → 0.35.0 and pushed `master` + tag `v0.35.0`. Cron is not documented as unable to push. - **README Updating:** documents scheduled `.gitea/workflows/update.yml` (run `./scripts/update.sh`, commit, tag `v$pkgver`, push; tag triggers build/release) and the human force path (`./scripts/update.sh` then commit/tag/push or PR on `develop` + `makepkg -si` / Releases). Release example is `v0.36.0` / `grok-bot-bin-0.36.0-1-x86_64.pkg.tar.zst`; until CI publishes that asset, `makepkg -si` works. PKGBUILD/README agree on 0.36.0. - **PR (not merged):** https://git.s1d3sw1ped.com/s1d3sw1ped/grok-bot-bin/pulls/8 (HEAD `49a15ebb2d1473666b7faed4a464a69c25eb64b5`)
linus closed this issue 2026-09-03 00:15:14 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
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#7
Delete Branch "%!s()"

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?