GHSA-5p4m-2wfm-xmqj (CVE-2026-59870) covers >=4.0.0 <4.3.1 and the fix was
not backported, so the existing >=4.3.0 override stopped clearing it and the
audit step in tests.yml now fails on every branch. It reaches us transitively
via eslint > @eslint/eslintrc > js-yaml.
Only the pinned floor and the resolved version move; integrity hashes are
untouched.
GHSA-rgw5-rvv9-x895 widened the affected range to <5.0.9, so the
existing >=5.0.8 override stopped clearing it and the audit step in
tests.yml now fails on every branch. Only the pinned floor and the
resolved version move; integrity hashes are untouched.
bun audit --audit-level high was failing on immutable (pulled in via
sass) for two DoS advisories (32-bit trie overflow, hash-collision
complexity). Bumped the override from ^5.1.5 to ^5.1.8.
bun audit --audit-level high was failing CI on transitive deps pulled
in by eslint and @sentry/vite-plugin. Existing brace-expansion
override didn't cover the patched range; added a js-yaml override.
When an unauthenticated user lands on the consent screen, push the authorization request server-side (RFC 9126 PAR) and round-trip only a short request_uri handle through login, instead of the full consent URL. The full URL — scope, 2KB state, PKCE and authorization_details — previously travelled inside the GitHub OAuth state during 'Sign in with GitHub' and could exceed the provider's state size limits, breaking MCP client logins.
- createPAR goes through an anonymous no-credentials client: the server serves /par (like /token) with wildcard CORS and credentials disabled, which the browser rejects for the SDK's default credentialed fetch.
- The post-login request_uri path requires a session before dereferencing (the handle is single-use and consumed even by failing authorize calls) and sends only clientId + requestUri, as the server rejects any other param alongside the handle.
- After authorize returns a grant, the URL is rewritten to ?grant_id= with replaceState so reloads resume via getGrant instead of failing on the consumed handle.
- The consent effect is keyed on the query string via $derived: login calls invalidate(ACCOUNT) right after goto(redirect), which replaces the page.url object without changing the query — an effect tracking page.url directly re-runs, cancels the in-flight authorize and re-dereferences the consumed handle.
- Expired/consumed handles render a friendly retry message; PAR failures (e.g. servers without the endpoint) fall back to the legacy full-URL redirect.
- resource params are forwarded with getAll (RFC 8707 repeats the key).
SDK pinned to the preview build of appwrite-labs/cloud#4660 (@4b3ae78); re-pin after the cloud PR merges. Models.Locale was renamed to Models.CloudLocale in that spec, updated the seven usages.
Refactor the consent screen for the per-project RAR model:
- Console access is now individually selectable: each account-tier scope
(teams.*, projects.*, organization.keys.*, domains.*) renders as a checkbox
with a real description; identity and account.admin stay read-only. The
chosen subset is sent as a downscoped `scope` to oauth2.approve (RFC 6749
§3.3) — bumps the @appwrite.io/console SDK to a build that exposes the param.
- Project access shows the actual project name + avatar + region per RAR entry
(resolved client-side via the user's orgs → listProjects), so the user can
tell which project each grant refers to. Unresolved ids fall back to the raw
id. Multi-project entries list all names (truncated past five).
- Sync the RAR type to the renamed `appwrite_project` (was `appwrite_console`)
and add splitSelectableScopes + project-name resolution helpers.
Authorize stays enabled whenever anything is granted (incl. identity-only).
The console OAuth2 consent screen rendered every requested scope as a flat
list. For broad requests (e.g. account.admin plus dozens of granular console
scopes) this produced an unusably long list.
Group granular scopes by resource and tuck them into a single collapsible
"App permissions" accordion, with read/write shown as compact tags. The
account.admin full-access row and the OIDC identity scopes stay as
always-visible rows above it.
Also bump @appwrite.io/console to 15.1.0, let the consent layout scroll a tall
card, and forward the resource indicator param through authorize.
bun audit (CI gate) flagged ws 8.19.0 (transitive via jsdom) for
GHSA-96hv-2xvq-fx4p. Add an overrides pin to 8.21.0, matching the
repo's existing security-pin convention.
Adds the 'Sign in with Appwrite' identity-provider UI for the Console
OAuth2 server — the two user-facing screens behind the new server env
vars:
- _APP_CONSOLE_OAUTH2_AUTHORIZATION_URL -> /oauth2/consent
- _APP_CONSOLE_OAUTH2_VERIFICATION_URL -> /oauth2/device
Consent (/oauth2/consent): authorization-code flow. Reads the grant,
shows the requesting app's branding and what authorizing grants, and
lets the user authorize or cancel. Approve redirects back to the
client with a code; cancel returns access_denied. The permission list
leads with full account access rather than the requested OIDC scopes,
since console-project tokens receive the full users (member) role
regardless of scopes.
Device (/oauth2/device): Device Authorization Grant (RFC 8628). When
opened via verification_uri_complete the code is rendered for the user
to confirm it matches their device (no silent auto-submit); otherwise
they type it in. After confirming, the same consent card is shown
(with device-specific copy), then a terminal success state.
SDK: bump @appwrite.io/console pin to 1a5604f which adds the Oauth2
grant service and Models.Oauth2Grant; wire Apps + Oauth2 into
sdk.forConsole.
Login: honor the redirect query param after email login (MFA-safe) so
OAuth2 flows resume after sign-in, aligning login with register.
Update SDK to @appwrite.io/console@82069e6 which exposes the new flag.
Replace supportsOrganizationRoles with supportsProjectSpecificRoles in
createMember, edit, and members page — org roles and project-specific
roles are now independently gated by their own plan flags.
Resolves critical advisory GHSA-5xrq-8626-4rwp. Updated store.test.ts
to use vi.useFakeTimers/vi.setSystemTime instead of the constructor spy
pattern that Vitest 4 no longer supports.
- New updateOAuth2Server.svelte card in project settings
- Enable/disable toggle, authorization URL, scopes, per-client token
durations with unit selectors, PKCE enforcement
- min={1} on all duration inputs, scopes sent directly to allow clearing
- Add ProjectUpdateOAuth2Server analytics event
Note: awaiting SDK with updateOAuth2Server method and correct enum names
Bumps @appwrite.io/console SDK to 35c3dea which introduces the Organization
class. All projects.list/create/update calls are now routed through
sdk.forConsole.organization(orgId) so requests carry the
X-Appwrite-Organization header required by the new API contract.