Release/store swarm cicd - #8
Conversation
Lets extensions be published from git/CI instead of the web form. The only backend gap was headless auth, so this adds long-lived publisher API tokens: - migration 0005_publisher_tokens (stores only the sha256 of the token) - mint/list/revoke endpoints; minting requires a real session (a leaked CI token can't mint more); store currentUser() resolves `tbpub_…` bearers - scripts/publish-extension.sh: zip → scp to files.profullstack.com → register the new version via the API with the token (generic; any CI) - docs/ci-publishing.md: token + SSH-key setup and a paste-in GitHub workflow scp upload + the version endpoint + slug lookup already existed, so CI reuses them. Typecheck clean; token mint/resolve/list/revoke round-trip verified. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Signed-in, bring-your-own-key endpoint that runs a deepagents-backed swarm.
Caller supplies provider + apiKey per request (transient, not stored — same
pattern as /api/models); anthropic uses ChatAnthropic, other providers use the
OpenAI-compatible adapter (incl. optional c0mpute.com GPUs). An optional `rubric`
enables the self-check loop. Mounted at /api/swarm, auth via currentUser.
Adds @logicsrc/agentswarm + deepagents + @langchain/{langgraph,anthropic,openai}.
Typecheck clean (Docker tsconfig), boots, route auth-gated (401 without session).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
- shared storeSession() persists a TronBrowser session token from any auth method; emailSignIn/emailSignUp hit the same /api/auth/login + /signup the website uses and store the returned token like CoinPay. - options UI gains the email/password fields. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
Warning Review the following alerts detected in dependencies. According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.
|
vu1nz Security Review0 finding(s) in PR #? No security issues found. |
No description provided.