Frames v2: retire manifest.name and the stored name - #32798
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 2 Skipped Deployments
|
flvndvd
approved these changes
Sep 21, 2026
davidebbo
force-pushed
the
frames-v2-drop-manifest-name
branch
from
September 21, 2026 12:23
74fb054 to
387e9c4
Compare
davidebbo
changed the base branch from
frames-v2-name-backfill
to
frames-v2-name-projection
September 21, 2026 12:24
davidebbo
changed the title
davidebbo
force-pushed
the
frames-v2-name-projection
branch
from
September 21, 2026 13:06
89ff507 to
691a386
Compare
davidebbo
force-pushed
the
frames-v2-drop-manifest-name
branch
from
September 21, 2026 13:06
387e9c4 to
15af165
Compare
The manifest no longer declares a name and useCaseMetadata no longer stores one. Zod is non-strict, so every manifest already written keeps parsing; the key is ignored from here on. Publication activation still records the description, which does come from the manifest. No backfill is needed: with the name derived from the Frame's path there is nothing stored to migrate.
Contributor
davidebbo
force-pushed
the
frames-v2-drop-manifest-name
branch
from
September 21, 2026 13:44
15af165 to
7b6319e
Compare
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
2 participants
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.
Second of five PRs. Removes
namefromFrameSourceManifestSchemaandframeNamefromFileUseCaseMetadata, now that PR #32795 derives the name everywhere.Zod is non-strict, so every manifest already written in production keeps parsing — the key is simply ignored from here on.
descriptionstays in the manifest and is still refreshed on every publication activation.No migration is needed and none is included. With the name derived from the Frame's path there is nothing stored to backfill, which is why the original backfill PR (#32797) is closed rather than merged — and with it the "run this in both regions before deploying" hazard.
Expect display names to change for Frames created before this: agents tend to write a prose
manifest.name("Two Truths and a Lie") and a terse folder name ("TwoTruths"), and the folder now wins.