Running newer 4.x container image on older 4.x database

I run our ghost blog using the ghost container image, and I’m curious whether I can deploy newer versions of the ghost (4.14) image pointed at a volume containing a pre-existing content directory/database created from a 4.11 deployment? It’s difficult to tell if there are database changes by doing diffs on releases. Is there any general rule regarding ghost version numbers as to when it’s safe or not safe to do this? Or when using containers (and not the cli to upgrade), should I always use a newly built content volume/database and import the content?

Ghost will automatically migrate the database when it starts up. General rule is to upgrade to the latest minor release available before going up a major release.

1 Like