Release Notes

Overview

We announce roughly every 2 months a new release. You can find more information in the sections below.

📬 Release Newsletter

Subscribe to the release newsletter to get notified with a rundown of the latest features and improvements as soon as a new release is ready.

Release Notes

  • Current Release: The latest announced release
  • Maintained Releases: Get security fixes and severe bug fixes.
  • Upcoming Release: You can already read about the features, improvements and fixes of the next release. But be aware that the release notes are auto generated and will be manually fixed before we officially anounce the new release.
  • Legacy Release: Legacy releases do not receive bugfixes anymore. If you use an old release please notify us (release@livingdocs.io) so we are aware and can inform you of critical fixes in newer releases.
NameUpcomingCurrentMaintainedLegacy
July 2022 Release✅
May 2022 Release✅
March 2022 Release✅✅
November 2021 Release✅
September 2021 Release✅
June 2021 Release✅
March 2021 Release✅
December 2020 Release✅
October 2020 Release✅
July 2020 Release✅
May 2020 Release✅
April 2020 Release✅
February 2020 Release✅
December 2019 Release✅
September 2019 Release✅
July 2019 Release✅
May 2019 Release✅
March 2019 Release✅
January 2019 Release✅
November 2018 Release✅
September 2018 Release✅
June 2018 Release✅
May 2018 Release✅
April 2018 Release✅
March 2018 Release✅
February 2018 Release✅
January 2018 Release✅
December 2017 Release✅
October 2017 Release✅
September 2017 Release✅
August 2017 Release✅
July 2017 Release✅

How to install a Livingdocs release/patch

Every release gets a label (dist-tag) as soon as it’s out. If you want to update your editor to the September 2021 release, you have to update your package.json like that:

// package.json with a label for the livingdocs editor
"dependencies": {
  "@livingdocs/editor": "release-2021-09",
  // ...
}

// As an alternative you can also use a version number with a ~ to only allow patch updates
// The minor (72) and major (13) version keep the same for every release, just the patch (38) version will be increased
// To find out the minor/major version for a release, you have to go to the release notes of a release and check the
// patch section
"dependencies": {
  "@livingdocs/editor": "~72.13.38",
  // ...
}

As soon as a maintained release is out, we only add bug fixes and security patches to a release. When a new patch version arrives, the label release-2021-09 will automatically moved to the latest patch version. This means, you can patch your project with this workflow:

// install definition in package-lock.json
npm ci

// get currently installed version
npm list | grep @livingdocs/editor

// update package-lock of the editor based on the definition of package.json
npm update @livingdocs/editor

// after the update you can check if the version has been updated
// and then you can commit the change
npm list | grep @livingdocs/editor

Info: Rili (Beta) is a small helper service to find out the latest version of a release.