Organizations, passkeys and a redesigned Envoy - #4

You have commit messages with errors ⧗ input: feat: projects limited to selected people, moving projects between teams, searchable people pickers - A project can be set to 'Only selected people': only the chosen team members (plus org owners and admins) can see it anywhere, including lists, search, CLI and API. New team members don't get access automatically, and removal from the team or org clears them from the list - Move a project, with its environments and values, to another team; refused if that team already has the same project URL; restricted projects keep only people on the new team - Add team member and Manage access use a searchable people list (name or email, arrow keys and Enter) - Both changes are recorded in the audit log ✖ body's lines must not be longer than 100 characters [body-max-line-length] ✖ found 1 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: feat: sign up with Google only; set a password in Account settings - The sign-up page only offers Google, so every address is verified. Password sign-up stays available for local development and tests (ALLOW_PASSWORD_SIGNUP) - Account settings → Password: set a first password without a current one (stays signed in), or change it (signs out everywhere). Email + password sign-in then works - Account settings hosts the new two-factor section ✖ body's lines must not be longer than 100 characters [body-max-line-length] ✖ found 1 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: feat: passkeys, optional two-factor, and an org setting to require it - Passkeys (WebAuthn) as a second factor: offered first at setup, used at sign-in, to unlock secret values and to generate backup codes; add, rename and remove them in Account settings - Only public keys are stored; challenges are single use and expire after 5 minutes; attempts are rate-limited - An enrolled account can't add a new passkey or authenticator app from a password-only session - Two-factor is now optional per account. Anyone who has a passkey or app always uses it; people without one see values directly - Organization settings → Security: owner-only 'Require two-factor authentication'. Existing orgs count as on, new orgs start off. Members without 2FA are blocked from a requiring org until they set it up (they can still leave); turning it off resets nothing - The last passkey or app can be removed only when no org of yours requires 2FA; an authenticator app can now be removed too - Owner 2FA reset also removes passkeys; the members list shows Needs 2FA / No 2FA ✖ body's lines must not be longer than 100 characters [body-max-line-length] ✖ found 1 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: feat: command menu searches environments and variable names - New /api/orgs/[org]/search finds environments and variable keys in the teams you can see (names only, never values) - Menu shows recently updated projects, teams, pages, actions and other organizations; substring matching instead of fuzzy; first result always selected - Opening a variable goes to its environment with the key filter set (?key=) - Project header: Use from CLI and the options menu are one button group ✖ body's lines must not be longer than 100 characters [body-max-line-length] ✖ found 1 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: feat: temporary links use the app's variables table, and say when they've expired - The KEY | VALUE table, value cells and .env import moved to a shared component used by the env editor and both share pages - Create page: Add variable / Import .env toolbar above the table, duplicate and invalid keys flagged; pages line up with the header like the app - Expired links answer 410 and are deleted on access; tokens carry their expiry so a link already cleaned up still reads

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v2. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/