On this year's Neos Conference I presented a session on updating Neos. I tried to answer three questions:

  1. Why you should be updating
  2. When you should be updating
  3. How to do updates

The slides

These are the slides for the session:

Summary

The very short version of the talk is:

  • Why?
    Because you get new features and bugfixes.
  • When?
    Whenever a new version is released.
  • How?
    Read & follow instructions, test & deploy.

Further reading

As promised, here are pointers to more background information. I tried to group them by topic.

Documentation

Keeping up-to-date

Security

Tools

Code adjustment examples

Luckily most of the changes that need to be done manually are very similar across projects. So the following changes done to the sites of the Neos project can serve as examples!

The update from Neos 4.3 to 5.3 for www.neos.io took a while… Most of that was due to a lot of changes around the marketplace package. Check out the PR at https://github.com/neos/Neos.NeosIo/pull/373

The docs.neos.io site has seen an update from Neos 5.3 to 7.1 (https://github.com/neos/Neos.DocsNeosIo/pull/59) and smaller upgrades for the following minor versions:

 

Updating Neos – Why, When and How © 2022 by Karsten Dambekalns is licensed under CC BY-NC-SA 4.0

Cover based on a photo by Clint Patterson on Unsplash