Can someone provide some clarity around the version property in the farcaster frame metadata tags?
 
Is it the manifest version? Related to the embed? Both? Neither? 
I originally hard coded it to "1" per the docs but was having trouble with the manifest until I later hardcoded it to "next" but I dont understand the purpose or what its used for 

cc: @deodad

@farcaster dev / dad / books, cooks, ski, code ~ there are many things of which a wise man might wish to be ignorant

Cohost of /gmfarcaster, a live stream Farcaster news show.  Engineer. Mom x 3.

that is exactly right

cc @dylsteck.eth any chance you can weigh on in the minikit question? would like to know so I can help devs

Manifest lives in well known farcaster json and purpose is for proving ownership and App Store listings?

And embed schema lives in the html header of every page and purpose is to give instructions for how to display the embed?

One thing that made it confusing for me is I used the base mini kit to get started and they are putting a lot of the files as env variables, and it’s not really obvious there are 2 places to maintain meta data fields 

I was using 1 as the version per the manifest docs (as an env var) but the embed didn’t work until I changed it to next 

Anyway… think I’m good for now. 
I’m just adding a bunch of new fields - tags, required chains, screenshots, etc

I see how this is confusing

there are two versioned schemas here:
- manifest
- embed

so two independent versions that are not related and happen to use different values

right now manifest has accepts '1' and embed accepts 'next'

will clean up in docs / figure out if we can make this simpler

patched up the docs and validations around the 1 v next confusion thanks for the callout