Directus stuck in a restart loop because of breaking changes

[msbt]

Hi there! A few of my Directus instances were down this morning after being updated to v10.10.0 and v10.10.1 respectively. This update brought potential breaking changes if you were using extension folders - which I did. Is it possible to look for "breaking changes" (especially in major updates like this one) in the future so they become updates that have to be applied manually instead of automatically?

Also, how is it again with the not-responding state of an app, is there an email notification at some point?

Best,
M

[girish]

@msbt mmm, we assumed the breaking changes were minor because this was released by Directus as 10.11 and not 11.0. See https://github.com/directus/directus/discussions/15435#discussioncomment-3883411 where it is confirmed they use semver. Maybe this is something to take up upstream?

There is no email for not-responding. Best to add a status notification app for now until we rework notifications.

[girish]

There are some further notes in https://docs.directus.io/getting-started/architecture.html#versioning . For them, "Minor — A new feature or meaningful improvement to an existing feature: may or may not be breaking."

I think Cloudron packaging has to follow what upstream does, otherwise, every minor release now becomes a major in Cloudron. Maybe best to turn off automatic updates for Directus and analyze each Cloudron package update?