Releases: alineacms/alinea
Releases · alineacms/alinea
v1.0.8
- Fix live previews for translated entries
v1.0.7
- Fix querying linked entries without locale
v1.0.6
- Fix querying linked entries - the requested locale was not passed
v1.0.5
- Alinea will now fail if linked entries cannot be resolved during querying.
Before it would log the error but continue - but this is rarely desired.
v1.0.4
-
Fix removing field contents in
Edit.update
. Pass anundefined
value to remove
field contents:await cms.commit( Edit.update({ id: '...', set: {removeMe: undefined} }) )
-
Fix processing link data correctly even it contains legacy data
v1.0.3
- Only access normalized config in next cms adapter. This fixes an error
in production builds which would prevent you from querying media files.
v1.0.2
- Tweak the withAlinea config function to work in all environments including
Next 14.
v1.0.1
-
Add the Infer.Entry and Infer.ListItem types which can be used to infer the
type of an entry or list item from a query.type Entry = Infer.Entry<typeof EntryType> const entry: Entry = await cms.get({type: MyType}) type ListItem = Infer.ListItem<typeof ListType> const list: Array<ListItem> = await cms.get({select: MyType.list})
v1.0.0
- Add support for Next.js 15 and Turbopack.
- Removed all previously deprecated options.
- Next.js config changes are now bundled in a
withAlinea
export found in
'alinea/next'. - Querying via
cms.find/get
is rewritten to take a single query object.
Have a look at the docs to see how to use the new query api. - Creating custom fields can now be done through
Field.create
. - Entries now have a single id. If you are upgrading and were using i18n you
can stabilize your ids by runningnpx alinea build --fix
.
v0.11.2
- Querying data in a Next.js edge route or middleware will forward the request
to your CMS handler. This will keep the code size of the edge route to a
minimum.