Skip to content

v4.130.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 25 Oct 13:30
· 48 commits to main since this release
v4.130.0
32f72ea

Find a project user's id

  • run402 auth users get --email <addr> [--project <project_id>] and r.auth.getUser(projectId, { email }) look one project user up by email (case-insensitive) and print { id, email, is_admin, is_test, email_verified_at, created_at }. Read-only, service key. Works for real members and for watermarked test users (is_test: true), so a role table keyed by user id can be seeded; tenant SQL cannot read the auth schema. No match fails AUTH_USER_NOT_FOUND, whose next_actions name how to create the user (a test-session mint for a <label>@<project_id>.test.invalid address).
  • run402 dev --as <label> prints the test user's id beside its email, with a ready role-row hint (run402 projects sql "INSERT INTO <role_table> (user_id, role) VALUES ('<id>', '<role>')").
  • run402 auth scaffold-roles points its first-operator bootstrap at auth users get.

Needs a gateway with GET /auth/v1/admin/users/lookup (live on api.run402.com). These changes are tagged in v4.129.1's source but were not in its published tarballs; 4.130.0 is the first release that ships them.

Deploys

  • A deploy request that got no response (Node fetch's 300 s header timeout, surfacing as X402_INITIAL_REQUEST_FAILED) is treated as transient: plan, poll and commit requests repeat, and a commit that never gets a response is NETWORK_ERROR, safe to retry, naming the operation. run402 deploy resume accepts --final-only.

Full Changelog: v4.129.1...v4.130.0

Assets 2
Loading