This document highlights the most important fixes, improvements, and features, that were introduced in Webiny
How To Upgrade?
Please check the Webiny 5.15.0 migration guide for the upgrade steps.
The majority of changes that were introduced in this release are related to the Amazon DynamoDB-only version of Webiny.
Amazon DynamoDB-only version of Webiny
In case you missed it, at the moment, Webiny relies on both Amazon DynamoDB and Amazon OpenSearch Service databases in order to store and retrieve data. And while this is definitely a good choice for larger projects, for smaller and mid-sized projects, we'll be introducing an Amazon DynamoDB-only version of Webiny. For now there are no official estimates when this will be available, but we can definitely say that a very large amount of work has already been done.
We extracted existing DynamoDB + Elasticsearch storage logic into
This allows us to create package that stores the data into DynamoDB only, or some other database.
sortis now a list of strings and default sort is
createdOn_DESC- you can check out the schema to see the fields you can sort by
pageargument is changed to
after- pass the
metaoutput was changed to be the same as in other apps
- the type
itemsinput and output are an array of JSON objects
We extracted prerendering logic into separate file,
@webiny/api-page-builder/prerendering, so it is now imported into
api/code/graphql/src/index.ts file. If you do not want to use prerendering of pages, feel free to remove the referenced import statement.
Due to changes in the way of how query building for Elasticsearch works we changed
ElasticsearchQueryModifierPlugin in the
It is an abstract class now, so if you used it to modify the query, please change it to either
Also, in that abstract class, method named
apply was renamed to
There are new
ElasticsearchSortModifierPlugin abstract classes, which are extended in each of the application that uses Elasticsearch. As their name suggests, they are specialized to modify either body or sort parameters of the Elasticsearch query.
For Page Builder check out
For File Manager check out
When consuming content via the read Headless CMS GraphQL API, the reference fields that might have been included in the GraphQL query would return entries in an incorrect order. From now on, this is no longer the case.
A special shout out to @nelsonchen5 for sorting this out! ❤️
Learn more about different types of the Headless CMS GraphQL API in this key topic.
The definition of Elasticsearch field now uses
CmsEntryElasticsearchFieldPlugin class instead of
Fixed a bug with missing
where parameter in the
listFiles query. Also added the
tag_and_in option to where so users can search for files that contain all given tags.
Also note that
search parameters in
listFiles query are deprecated. Use the
where parameter instead.
Webiny CLI -
--help Argument Now Works as Expected (#1926, @snstanton)#
When using the Webiny CLI, the
--help argument now works as expected.
Special thanks to @snstanton for taking care of this! ️️❤️