In case of a regression introduced in Production after the upgrade, a rollback to your previous liana is the fastest way to restore your admin panel.
CORS allowed headers
Every collection calls (CRUD operations) to your agent will now be performed with a new header called Forest-Context-Url . This header contains the current URL of the user performing requests. This can be handy if you need information on the context this user is working on.
If you don't have any restriction on headers within your CORS configuration, nothing needs to be changed, you can move on to the next section.
If you have configured a header whitelist (allowedHeaders in express for instance) in your CORS configuration, you need to add this new header to the whitelist, otherwise browsers won't trigger request anymore due to CORS policy:
Until now, once you had submitted a file for upload, the file name wasn't persisted. We have now made so that it is possible to save and display it.
If you use a regex to parse data before sending it for upload (like we originally suggested in this Woodshop tutorial), there is a breaking change: you need to use the output of the parseDataUri method.
const field = fields.find(field=> field.field ==='a field');
field.value ='what you want';
The signature of hooks functions has changed. In order to support hooks for global and bulk smart actions, record is no longer sent to the hook. You must change the way you get the record informations. This change also prevents unnecessary computation in case you don't need to access the record(s) inside the hooks.