Apostrophe 3 Beta 3 #3144
agilbert
announced in
Release Notes
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone, this week we published Apostrophe 3 Beta 3.
This is planned to be our last Beta release before 3.0.
This cycle we continued to focus on bug fixing, with one notable enhancement being the upgrade of our rich text editor to use tiptap 2. Excited to continue buttoning things up over the next two weeks in preparation for the 3.0 release, after which we'll be focusing quite a bit on migrating critical extensions from 2.x as well as additional enhancements for the editing tools.
Apostrophe 3.0.0-beta.3
Security Fixes
The
nlbrandnlpNunjucks filters marked their output as safe to preserve the tags that they added, without first escaping their input, creating a CSRF risk. These filters have been updated to escape their input unless it has already been marked safe. No code changes are required to templates whose input to the filter is intended as plaintext, however if you were intentionally leveraging this bug to output unescaped HTML markup you will need to make sure your input is free of CSRF risks and then use the| safefilter before the| nlbror| nlpfilter.Adds
ignoreUnusedFolderWarningoption for modules that intentionally might not be activated or inherited from in a particular startup.{% render fragmentName(args) %}.Fixes
sanitize-htmlandnodemailerto new major versions, causing no bc breaks at the ApostropheCMS level. This resolved two critical vulnerabilities according tonpm audit.localized: falseorautopublish: true,as well as singleton types, now display the correct options on the "Save" dropdown.ignoreUnusedFolderWarningoption for modules that intentionally might not be activated or inherited from in a particular startup.Notices
npm auditvulnerabily warnings relating topostcss7.x were examined, however it was determined that these are based on the idea of a malicious SASS coder attempting to cause a denial of service. Apostrophe developers would in any case be able to contribute JavaScript as well and so are already expected to be trusted parties. This issue must be resolved upstream in packages including bothstylelintandvue-loaderwhich have considerable work to do before supportingpostcss8.x, and in any case public access to write SASS is not part of the attack surface of Apostrophe.Changes
Apostrophe 2.120
apostrophe (core) 2.120.0
autoCommitPageMovesflag in workflow to commit all page moves automatically, manages error notification.apostrophe-multisite 2.11.1
mongorestoreutility.apostrophe-cli 2.3.7
apostrophe-workflow 2.39.0
autoCommitPageMovesflag to commit all page moves automatically.Have a great weekend ✌️
Beta Was this translation helpful? Give feedback.
All reactions