A start command names an entrypoint belonging to one framework. Carrying it
across a switch submits it against a runtime that has no such entrypoint,
and a switch to static leaves a command the form no longer shows.
Reset it alongside the other framework-derived fields, and send it only for
the ssr adapter, matching the fallbackFile line beside it.
The create-site flows read startCommand off a framework adapter and
offered it as a prefilled value and a placeholder. The API never returns
that field - FrameworkAdapter does not declare it - so the reads always
resolved to undefined, and the cast that made them typecheck was the only
thing hiding it. Had the field ever been returned, the console would have
put an internal runtime command in front of every user creating a site.
Drop the field from the create flows entirely and let the server pick its
own default. In site settings the input stays, but it moves under a
collapsed Advanced section, loses the Reset-to-default button that had
nothing to reset to, and takes a generic placeholder.
bun audit fails the CI build on three high nanoid advisories. All fixes are
within the existing semver ranges: the direct dependency and @melt-ui/svelte's
nested copy move to 5.1.16, and the 3.x copies under @ai-sdk/provider-utils
and postcss move to 3.3.17.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Appwrite's apps.get()/apps.list() no longer resolve CIMD URLs — appId is
always a plain ID now. Detect URL-shaped OAuth2 client IDs in the console
and fetch the Client ID Metadata Document directly from the browser,
mapping its RFC 7591 fields onto Models.App for consent/device/applications
rendering. Fetch or validation failures fall back to hostname-only branding
so the flow never blocks.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
The string fallback in the row column renderer exists for the spreadsheet
inline cell editor, where an entire array is edited as one comma-separated
textarea. It keyed off `column.array` (the column definition) rather than
the `array` prop (the render mode).
In the full row create/edit form, columnItem renders one Column per array
element and deliberately omits the `array` prop so each item gets its
element-type input. Since `column.array` was still true, every item
collapsed to a string input -- a Boolean[] column showed "Enter string".
This also caused intermittent save failures: the string component still ran
parseValue() against column.type, so literal true/false/1/0 coerced and
saved, while anything else yielded null, and a null inside a typed array is
rejected by the API.
Keying off the `array` prop restores per-item typed inputs (boolean select,
number input with min/max, date picker) while leaving the spreadsheet cell
editor and its "Advanced edit" link untouched, since only the two
fromSpreadsheet branches pass `array`.
Two of the three added comments restated the expression next to them. Keep
only the one carrying the upstream fact — that the API serializes a missing
seat `limit` as `0` — and leave the rest of the reasoning in the commit
message and PR body.
`getServiceLimit('members')` returned `plan.addons.seats.limit ?? 1`. The
Appwrite starter plan's seats addon omits `limit`, and the API serializes
the missing value as `0` — which is not nullish, so the `?? 1` fallback
never applied and the limit came back as `0`.
`checkForUsageLimit` then read that as "no members allowed":
membersOverflow = Math.max(0, organization.total - 0) // always >= 1
so every free-plan organization was flipped to read-only, which silently
disables project creation, member invites and the other write actions
gated on `readOnly`. The explanatory banner never showed either, because
`limitReached.svelte` is gated on `!billingPlanDetails.usage` and the
starter plan's `usage` serializes to a truthy object — leaving a
greyed-out "Create project" button with no reason given.
Normalise a zero limit to `Infinity` in `getServiceLimit` so every caller
agrees, and only treat a real, positive cap as exceedable so a bad limit
can't take an organization read-only again. The UI call sites already
worked around this with `getServiceLimit('members', ...) || Infinity`;
`checkForUsageLimit` was the only consumer that did not.
Plans that set an explicit seat limit (the Imagine plans use 1) are
unaffected, as are Pro, Scale and Education, which declare no seats addon
and already returned `Infinity`.
The card had no permission check, so a reader saw a delete control that
only failed once confirmed. The rest of the feature already derives that
from messages.write: the list gates its create button and row selection
on it.
Gate the card the same way, so it tracks permission rather than status.
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.
The delete card was hidden while a message sat in processing, so a
message a worker never finished could not be removed from the console at
all. The server no longer rejects that delete, so the card can always
render.
Editing stays gated where it already was; only removal is unblocked.
loadGridRows builds its queries twice on the fallback path, and loadPage
passed a Map iterator that the first build exhausted - the retry then ran
without the active filters and paged in rows outside them.
Tables with wide relationships make the API exceed its own 500 value
limit while resolving them for a full page of rows, failing the whole
listRows request and rendering a 400 error page instead of the table.
Retry the page without relationship selects when that happens, then fill
relationships in over chunks of 10 rows. Rows whose chunk still fails
render without relationship data instead of taking down the page.
Tables that load today are unaffected - the fallback only runs after a
'greater than N values' failure.
The project Settings > Usage tab failed to render entirely, while every
other Settings tab worked. The API request succeeded; the crash was in
the page component's render:
Uncaught TypeError: Cannot read properties of undefined (reading 'length')
at +page.svelte:324
`data.usage.executionsBreakdown` was undefined. The console SDK types it
as a required `MetricBreakdown[]`, so the guard read `.length` on it
unconditionally. Because a throw during render aborts the whole render
pass, nothing mounted -- which is why the tab highlight moved to Usage
while the previously active tab's content stayed on screen instead of an
error page being shown.
Optional-chain both breakdown-table guards (`executionsBreakdown` and
`authPhoneCountryBreakdown`) so a missing breakdown hides just its table.
Also guard two latent instances of the same class on this page, since the
response demonstrably omits array fields the SDK types as required:
- `legendData` reduced over `databasesReads`/`databasesWrites` outside any
`{#if}`, so it would have crashed even earlier had those been missing.
- The db chart's `{#if dbReads || dbWrites}` passes when only one array is
present, but the body mapped both.
These are null-guards rather than defaulting the arrays to `[]`, because
`[]` is truthy and would flip several `{#if}` empty-state checks, silently
replacing "No data to show" cards with empty charts.
Separately, the attribution ping in `+layout.svelte` was fire-and-forget
with no `.catch()`, so a blocked request surfaced as an unhandled
`Failed to fetch` rejection that obscured real errors in the console.
When project is missing but an error query param is present, display the actual OAuth failure instead of the misleading "Missing redirect URL" message.
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
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.
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.
A prior bun update/install cycle on this branch stripped the sha512
checksums for @appwrite.io/console, pink-icons-svelte, and
pink-svelte (flagged in review). Restored them to match main's
pinned versions.
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.
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.
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.