build(devcontainer): install tea cli and mount the signing key #26

Merged

TJC merged 4 commits from chore/devcontainer-tea into main

2026-08-18 10:40:03 +01:00

Bolt commented

2026-08-18 10:39:13 +01:00

Collaborator

Summary

track devcontainer-lock.json, pinning node and claude-code-passthrough to resolved digests
install tea 0.15.0 from a per-arch download verified against a pinned sha256
register the tea login in post-create from GITEA_SERVER_URL and GITEA_SERVER_TOKEN, so a rebuild does not lose it and the token stays out of any tracked file
bind-mount the commit signing key at its host path, so the global user.signingkey needs no container-specific override
postCreateCommand moves into post-create.sh now that it does more than pnpm install

Test plan

rebuilt the container: tea --version reports 0.15.0 and tea logins list shows the ai login
git log --format=%G? reports G for all three commits on this branch
sha256sum -c gates the install; a mismatch fails post-create

## Summary - track `devcontainer-lock.json`, pinning node and claude-code-passthrough to resolved digests - install tea 0.15.0 from a per-arch download verified against a pinned sha256 - register the tea login in post-create from `GITEA_SERVER_URL` and `GITEA_SERVER_TOKEN`, so a rebuild does not lose it and the token stays out of any tracked file - bind-mount the commit signing key at its host path, so the global `user.signingkey` needs no container-specific override - `postCreateCommand` moves into `post-create.sh` now that it does more than `pnpm install` ## Test plan - rebuilt the container: `tea --version` reports 0.15.0 and `tea logins list` shows the `ai` login - `git log --format=%G?` reports `G` for all three commits on this branch - `sha256sum -c` gates the install; a mismatch fails post-create

Bolt added the

chore

label

2026-08-18 10:39:13 +01:00

Bolt added 3 commits

2026-08-18 10:39:13 +01:00

build(devcontainer): track the feature lock file f47b6b3bac

- pins node and claude-code-passthrough to resolved digests

build(devcontainer): install tea cli and mount the signing key 36489c5c06

- the forge is forgejo; tea is how issues and PRs get created
- pinned per-arch sha256, verified before install
- postCreateCommand moves into a script now that it does more than pnpm install
- bind the commit signing key at its host path so commits stay verified

build(devcontainer): register the tea login from the host token 290fdb145e

- a rebuild discards ~/.config/tea, so post-create re-adds the login
- GITEA_SERVER_URL and GITEA_SERVER_TOKEN come in via containerEnv
- tea reads both directly, keeping the token out of any tracked file

TJC added 1 commit

2026-08-18 10:39:55 +01:00