Dev key creation is no longer allowed. Removes the create button,
create modal, empty-state create action, and command palette entry,
and adds a deprecation alert linking the changelog:
https://appwrite.io/changelog/entry/2026-07-22
sites.getUsage() is being dropped from the SDK (appwrite/sdk-for-console#105),
along with the other usage endpoints removed in #3134. This inline
build-metrics card on the site deployments page was the one live
consumer that cleanup missed.
Removing every remaining usage/[[period]] route in this branch left
the shared Usage/UsageMultiple components (src/lib/layout) with no
consumers, which also broke type-checking since no route defines a
`period` param anymore. Extracted the still-used helper functions
(periodToDates, total, etc.) to a plain usageHelpers.ts and deleted
the dead components. Also removed a leftover "Usage" sub-navigation
entry in the database store.
Removes the Usage tab/route and its g-u command-center shortcut for
buckets, functions, sites, and auth — the same cleanup already done
for databases (#3128/#3130/#3131). Project-level billing usage
(settings/usage) is untouched.
Same cleanup as #3128/#3130: removes the per-database Usage tab
(database-[database]/usage) and its command-center shortcut. It
called tablesDB.getUsage(), which is going away with the backend
usage-endpoint removal.
Same cleanup as #3128, one level down: the per-table Usage tab still
called tablesDB.getTableUsage(), which is going away with the backend
usage-endpoint removal and is already showing empty data on cloud.
Storage, functions, and sites already dropped their all-time usage
tabs; databases still had one, plus orphaned usage route files and a
dead command-center shortcut across storage/functions/sites/databases.
Gitea is a self-hosted-only feature, not offered on Appwrite Cloud, so
the button now checks isSelfHosted in addition to _APP_VCS_PROVIDERS.
Swapped the placeholder teapot silhouette for Gitea's actual mascot
mark.
Gated behind _APP_VCS_PROVIDERS containing 'gitea' (server-side allow
list), so it stays hidden unless Gitea is actually configured. Ships
a stand-in monochrome icon since no Gitea icon exists in
@appwrite.io/pink-icons-svelte yet.
Replace heading-string matching with an explicit collapsible flag on
PermissionGroup, use startsWith instead of full-text search for the
organization picker, and reset loadingMore via finally on stale-term
early returns.
Co-authored-by: Cursor <cursoragent@cursor.com>
Recognize both hosted MCP resource URIs, add missing organization scope
descriptions, make permission groups collapsible, paginate project and
organization pickers with infinite scroll, remove per-scope copy buttons,
and add account switching via a dropdown on the account chip.
Co-authored-by: Cursor <cursoragent@cursor.com>
Mirrors the truthiness guard already used in columns/+page.svelte, so
an empty-string format from the API falls back to undefined instead of
failing to match any option and dropping the icon.
The create-index column selector matched icons by type only, so enum
columns (type: string, format: enum) fell through to the first
string-typed option and showed the email icon. The columns table also
showed an "Indexed" checkbox for relationship columns, which can't be
indexed.
Follow-up to #3111 (Greptile review): the collection header still rendered a
'Usage' tab linking to ${path}/usage, whose route was deleted in #3111. It
would 404 for multi-db users. Remove the tab entry.
The per-service DocumentsDB usage endpoints were removed in cloud
(appwrite-labs/cloud#4679, 'remove per-service /usage endpoints') as they
duplicated the org/project usage surface. The console collection usage page
was the only consumer of documentsDB.getCollectionUsage, so remove it and its
command-center 'Go to usage' entry. Database/table/project usage pages are
unaffected (they use the retained tablesDB.* usage endpoints).
- Hoist the flow out of the 220-line effect into one named function per
entry branch (grant_id / request_uri / raw client_id), cancelled via a
run counter instead of a closed-over flag.
- Dedupe the authorize-request param extraction shared by createPAR and
authorize into readAuthorizeParams(), plus getAccount()/fail() helpers.
- Move error messages and the oauth2_invalid_request exception type into
a colocated errors.ts.
- Build navigation targets with resolve() to satisfy
svelte/no-navigation-without-resolve.
Greptile follow-up: the PAR path already used params.getAll('resource') but the authenticated direct-authorize call still sent only the first value, dropping repeated RFC 8707 resource indicators.
Greptile flagged the message.includes('request_uri') heuristic as over-broad. Match the AppwriteException type oauth2_invalid_request instead — the server reports every dead-handle case (expired, consumed, malformed) under that type, and since the request_uri authorize call sends nothing but the handle, the type can only mean the handle is unusable. Verified against the local cloud branch: a consumed handle returns type oauth2_invalid_request with message 'Invalid request_uri.' (which the suggested 'expired'/'not found' substrings would have missed).
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.
Project-scoped addon resources (addon_premiumGeoDB) are rebuilt by the cloud
project aggregator without a `name` field, so the per-project breakdown rows —
which used `addon.name || addon.resourceId` — rendered the raw resourceId.
Add premium geo entries to billingAddonNamesFallback and apply the map in the
breakdown rows too (previously only the top-level addons section used it), so
the label degrades to "Premium Geo DB" instead of "addon_premiumGeoDB".
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
handleReEnable discarded the createPremiumGeoDBAddon return value and always
reported success. If the endpoint returns a PaymentAuthentication (payment/3DS
required) instead of an Addon, the challenge was never initiated — the addon
would sit in `pending` while the UI claimed it was re-enabled.
Mirror the enable modal: detect the `clientSecret` branch and drive confirmPayment
(which redirects to ?type=confirm-addon so the existing onMount handler completes
the payment). Matches BAA.svelte's handleReEnable pattern.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Audit logging has permanently stopped writing to the old project-DB
audit collection cloud reads from -- account, users, teams, messaging
topics, and database tables/collections Activity tabs (plus the
per-row/document activity side sheets) can never show new data again,
and are broken outright wherever the underlying endpoint was never
restored. Removes the tabs, command-palette entries, and the now-dead
route/component files rather than leaving broken or permanently-stale
screens in the product.