Alpha release checks
The gateway has public alpha releases on GitHub.
The Python package is on PyPI from v0.1.0-alpha.10. Protocol version is 0.1.0.
On this page
Prepare a release
- Run the repository checks and
uv build. - Review the source, dependency notices and package contents. Keep secrets and local logs out of the release.
- Let the release workflow write and check
SHA256SUMS(below). - Test the exact component commits in the hub compatibility manifest.
- Update the release notes and evidence links. Separate simulation, physical tests and Grok Bot results.
- Obtain the owner's approval for publication. Use
devfor integration andmainfor releases. - Pin hub documentation snapshots to released component commits before a hub release.
Publish a release
- Run the repository checks and
uv build. - Merge the release PR into
main. Tag it, for examplev0.1.0-alpha.7, and publish the GitHub release. The owner approves each step. - In Actions → release packages → Run workflow, choose
mainand enter the tag. The workflow checks that the tag matches the package version. It builds the wheel and the source archive and writesSHA256SUMSwith plain file names. It checks that file in a fresh folder and attaches all three files to the release. It never replaces an asset. - To upload to PyPI, run it again with Also upload to PyPI. The upload uses trusted
publishing: GitHub gives the job a short-lived identity, and no PyPI token is stored.
The
pypienvironment waits for the owner's approval.
Check a download
mkdir release-check
cd release-check
gh release download v0.1.0-alpha.7 --repo adidshaft/grok-gadgets-gateway
shasum -a 256 -c SHA256SUMS
Releases made before this workflow may list dist/ paths in SHA256SUMS
(hub #151).
One-time PyPI setup (owner)
- Sign in to pypi.org with two-factor authentication on.
- Open Your projects → Publishing → Add a new pending publisher → GitHub. Enter
PyPI project
grok-gadgets-gateway, owneradidshaft, repositorygrok-gadgets-gateway, workflowrelease.ymland environmentpypi. - In GitHub, open Settings → Environments → New environment, name it
pypi. Addadidshaftas a required reviewer. Under deployment branches, allow onlymain.
The first approved upload creates the PyPI project. After that, the pending publisher
becomes a normal trusted publisher for grok-gadgets-gateway.
Original source uses Apache-2.0. See NOTICE for dependencies and SECURITY for private reports. GitHub issues track current work. Keep local issue IDs in commits so contributors can follow the evidence.
Evidence limits
The owner tested one ESP32-S3 OLED kit over USB and Wi-Fi on 12 October 2026.
Grok Bot ran local shell commands through rehearse. On 13 October 2026 it also called the six tools natively from the Mac and the iPhone through serve --oauth behind an owner-run tunnel. An independent second installation remains unverified.
The Wi-Fi kit needs a running gateway. From 0.1.0-alpha.13 that can be an always-on Linux server instead of the Mac; the owner's kit passed this on 13 October 2026 (record).
From 0.1.0-alpha.14, factory-provision prepares a gadget so a person joins it to Wi-Fi from a phone alone; the owner's kit passed this on 14 October 2026 (record).
From 0.1.0-alpha.15, serve --oauth --accounts lets each person claim a gadget with the code on its screen and see only their own gadgets; two people passed this on the owner's relay on 17 October 2026 (record).
From 0.1.0-alpha.16, the relay sends signed firmware updates to gadgets that ask for them (firmware sign, add, assign, status); the owner's kit passed this on 17 October 2026 (record).
From 0.1.0-alpha.17, relay init, relay-check --mcp, enroll --batch/--count and builder report help a builder set up a relay and ship gadgets; a clean-room run and the owner's dry run on a fresh host passed on 17 October 2026 (record).
From 0.1.0-alpha.18, long-poll (wait_ms), sign-in by Client ID Metadata Document, a minimal sign-in page, oauth watch, fleet and serve --max-devices; a fresh 512 MB relay carried 1,000 simulated gadgets with long-poll on 18 October 2026 (record).
From 0.1.0-alpha.19, the sign-in page shows one instruction, one field and one button; the owner approved it from phone-size screenshots on 20 October 2026.
From 0.1.0-alpha.20, serve --credits keeps credits per account with signed receipts and the credits commands (hub ADR 015 Stage 0); no payments (record).
From 0.1.0-alpha.21, backup writes a mode-0600 archive of the config directory with its SHA-256; a restore into an isolated config home matched credits verify, accounts list and firmware list in a local rehearsal on 24 October 2026 (hub #418).