Why does Payload stop working with almost every update, in subtle and difficult to debug ways?

[CaptainN]

In the most recent update I got multiple problems:

• It's now always loading the live preview, even when the pane isn't open - WHY? It's os irritating, and it loads it like multiple times. My preview site is behind basic auth, and the thing can't remember the password when accessed this way. What were you thinking?
• I also can't seem to update a change to a previously published page - it just fails silently, despite there being a clear (and baffling) error in the network logs.

It really feels like this is just run on vibes, and bubble gum.

[CaptainN]

I think this might be from a missing version bump migration - this is EXTREMELY hard to surface - dev mode just applies these, and then in production I'm left with baffling errors, that don't trigger any ui feedback - at all.

[CaptainN]

In this case, it seems to be because of some change to the snapshot system. Am I really supposed to read through a dozen dense minor version bump release pages to figure this out?

[CaptainN]

ARGH, looks like it's #14217

[CaptainN]

In the API tab, I can see the JSON blob doesn't get updated, but I also get this undefined value in core generated link for a feature (locale) that I DON'T use, or have configured - and have never had configured. THis does gum up my server logs...

https://[myinstance]/api/pages/13197?depth=2&draft=false&locale=undefined&trash=false

Sloppy...

[DanRibbens]

In this case, it seems to be because of some change to the snapshot system. Am I really supposed to read through a dozen dense minor version bump release pages to figure this out?

We are extremely careful not to introduce breaking changes in minor updates, this includes schema changes that would need require a db migration. There are edge cases where we allow changes that could need a new migration, but only in cases where existing queries would not error if the migration was not ran.

ARGH, looks like it's #14217

I'm not sure how this is related to the above mention of errors.

In the API tab, I can see the JSON blob doesn't get updated, but I also get this undefined value in core generated link for a feature (locale) that I DON'T use, or have configured - and have never had configured. THis does gum up my server logs...

I agree we could drop the locale query param in this instance, but it shouldn't change the data you're getting back in any way.

[DanRibbens]

Are you still struggling?

I also can't seem to update a change to a previously published page - it just fails silently, despite there being a clear (and baffling) error in the network logs.

What is the error you were getting?

[CaptainN]

I had to dive in to the database and fix things directly in there. I never got the update function to work.

I don't recall the specific error, but it was an error coming out of an update operation at the drizzle layer. It may have been a missed migration from a minor version update (there was just another one one of those in a more recent update - which my skills.sh skill, which is specifically instructed to read release notes when updating, missed entirely.)