v0.8.54: org apis, file search optimizations, document caching fix - #8130
Merged
Merged
Conversation
waleedlatif1
commented
Sep 22, 2026
waleedlatif1
commented
Collaborator
- fix(access-requests): clarify request navigation and empty states (fix(access-requests): clarify request navigation and empty states #8125)
- fix(workspace-files): keep the file-search claim on the ordered pending index instead of a hash join (fix(workspace-files): keep the file-search claim on the ordered pending index instead of a hash join #8128)
- fix(knowledge): make connector syncs resilient to removed credentials, partial outcomes and slow completion counts (fix(knowledge): make connector syncs resilient to removed credentials, partial outcomes and slow completion counts #8126)
- feat(api): expose organization access and usage operations (feat(api): expose organization access and usage operations #8127)
- fix(files): stop promising immutable caching for documents compiled against other files (fix(files): stop promising immutable caching for documents compiled against other files #8129)
…ng index instead of a hash join (#8128)
…, partial outcomes and slow completion counts (#8126) * fix(knowledge): leave a connector whose credential was removed unscheduled instead of walking the failure ladder to disabled * fix(knowledge): report a partial connector sync as an outcome instead of failing the run * fix(knowledge): count a connector's documents before the completion locks and index the live set * fix(billing): serve execution admission from the usage gate cache instead of re-summing the billing period per run * fix(knowledge): share the unscheduled connector write, scope credential removal to content-engine modes, and keep both sync holds visible * fix(knowledge): keep the corpus size on a failed completion count, unschedule only connectors left without an auth source, and give fixture connectors a credential * fix(knowledge): skip a required-key connector without a key and write the unscheduled state only over the row the run observed * fix(knowledge): release a dispatch-marked pending row when its credential is missing * fix(knowledge): assert the billing owner before the credential-missing terminal write * fix(knowledge): stop offering reconnect once a connector holds a credential again
* feat(api): expose organization access and usage operations * fix(api): enforce current invitation and organization scope * fix(billing): serialize credit caps with access revocation * fix(workspaces): align detachment with invitation lock order
…gainst other files (#8129) * fix(files): stop promising immutable caching for documents compiled against other files A versioned serve URL (`?v=<updatedAt>`) was always answered with a one-year `immutable` Cache-Control. That holds for a stored source — a content write rotates the storage key, so a given key's bytes never change — but not for a response the route resolves against OTHER files: a document compiled against the files it references, or a sim page inlining its images, recompiles on every request. Those bytes change when a referenced file changes, while this file's key and `updatedAt` stay put, so the whole URL is unchanged and the browser served a stale render from cache until the document itself was edited. The resolver now reports when it read referenced content, and the route withholds the immutable lifetime for exactly those responses, keeping it for stored sources and self-contained artifacts. Also corrects three comments that claimed generated docs are edited in place under the same storage key. That stopped being true in #5545 (2026-07-13), which made every content write allocate a new key; the caching rule above was reasoned from the stale claim. * improvement(files): make serve cacheability a declared, required property An optional boolean let a branch added to the resolver inherit the cacheable default by saying nothing — the exact failure this change exists to prevent. Cacheability is now a required field every branch must declare, so forgetting it fails the build rather than silently promising a year of immutability. * improvement(files): answer a file revalidation with 304 instead of the whole body A response the browser is told to revalidate carried no validator, so every check re-sent the entire file. That is the cost a document compiled against other files now pays on each window focus: it cannot be given a cache lifetime, because its bytes really may have changed, so the only way to make the check cheap is to let the client prove what it already holds. Authorized serves now carry an ETag — the digest of the bytes about to be sent, which is exact by construction however those bytes were produced — and answer 304 to a matching If-None-Match. Matching is weak, per RFC 9110, so a cache that stored a weak validator still revalidates. Kept out of createFileResponse deliberately: digesting costs a pass over the buffer, up to the 100MB transfer ceiling, and a response served as immutable is never revalidated, so it would pay that pass and never collect. Public assets and the assistant-image path are unchanged. * fix(files): report a reference dependency from the isolated-VM compile path The isolated-VM fallback returns before the static reference scan, so a document it compiled never reported one — yet that path reads workspace files live through its broker, which is what `onWorkspaceFileAccess` records. A versioned request for such a document therefore still took a one-year immutable lifetime, and changing a referenced file left the browser serving a stale render. Fixed at the root rather than in that one branch: the flag is now required on CompiledDocResult, so every compile path must declare it and a new one cannot inherit a cacheable-forever answer by staying silent. Each site reports the union of what the source references statically and what the compile actually touched — neither alone is sufficient, since a failed read records no access and the broker reaches files the static scan cannot see. Making it required immediately surfaced a second case: the process-local compile cache is shared with compiles that carried a workspace, so a cached entry can hold contributor identities even when the reading call passes none. That branch now reads the cached identities instead of assuming independence. * improvement(files): compute a validator only where a response can be revalidated Both reviewers caught the same contradiction: the digest was documented as worth paying only where a 304 can be collected, then applied to every authorized serve including immutable ones, which are never revalidated. One place now decides, so an immutable response takes the plain path and spends no pass over its buffer. Also drops a redundant translation. The resolver was converting the compiler's boolean into a string union and the cache rule was converting it straight back; the producer's own required boolean now travels end to end, which is one fact in one shape and keeps the same build-time guarantee that a new branch must declare it.
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
Contributor
 |
This branch was previously deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.