Upgrading from 1.0 to 1.1/1.2
1.1 is the development series which will lead to the next stable series, 1.2. To upgrade before 1.2 is released, you should choose the "next" tag when choosing versions for upgrade, or if upgrading from the command line, us the npm "next" tag:
npm install @saltcorn/cli@next
Here are some changes you should be aware of which may break your application on upgrade:
- Node 18 is the minimal Node.js version we are targeting, and Node.js 22 is the preferred version. We will no longer make efforts to ensure Saltcorn 1.1 and later run on Node.js 16.
- As noted in the security notes, Saltcorn 1.0 did not check read access to the table that supplied values for dropdowns. This is now checked. You should verify that all dropdown selects work as expected, and if not adjust table read permissions
- As noted in the security notes, Saltcorn 1.0 did not check the minimum role to run views when these were embedded in other views or pages. In 1.1.1, this will trigger a warning that you can look for in you logs. with this text: WARNING: running embedded view {{view name}} without role permission. In 1.1.2 and onwards, this warning will no longer be issued, and the view run will result in a blank string.
- The above change also applies to Login and signup forms as well. These need to have a public role to access. To prevent you from being locked out of the system, we have inserted a check to run the standard login form if there is no access to public for you login and signup forms.