Rename package to scoped @valknar/triggershell
CI / Checks (push) Successful in 46s
CI / Publish to npm registry (push) Successful in 48s

Matches vpinball-wasm's move back to a scoped name: an unscoped
package on this Gitea npm registry can't be mapped via a normal
`.npmrc` `@scope:registry=` entry, since the registry doesn't proxy
npmjs.org. Scoping lets any consumer add one registry line instead of
pinning a tarball URL per dependency.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012hQoM3jJT1Lx7CMTciMzvD
This commit is contained in:
2026-08-23 01:06:23 +02:00
co-authored by Claude Sonnet 5
parent 90d68f2510
commit e5a1b7ce53
2 changed files with 3 additions and 3 deletions
+1 -1
View File
@@ -24,7 +24,7 @@ API for automation.
## Quickstart
```bash
npm install -g triggershell # or: npx triggershell <command> for one-off use
npm install -g @valknar/triggershell # or: npx @valknar/triggershell <command> for one-off use
triggershell init # scaffold triggershell.yml (+ .env for secrets) in the current directory
triggershell users add admin # create a login (skip if you set auth.enabled: false)
triggershell start # start the app and open the browser