Manuel

> ## ⚠️ Important change for merging PRs from Parse Server 5.0 onwards! > > We are planning to release the first beta version of Parse Server 5.0 in October...

Concerted to draft: - If this means a breaking change, we may as well break for a more sustainable solution, see https://github.com/parse-community/parse-server/pull/7440#discussion_r678916891. - We don't introduce breaking changes this way...

Is it currently possible to write this feature yourself in Cloud Code. However, it would surely be nice to have such a feature built in. Do you want to open...

That method would be a good source of inspiration. It has everything you will also need for the new route.

I think we also need an internal token (like with password reset), because: - a) The deletion email link needs to expire for security reasons - b) The endpoint to...

Interesting that a patch version upgrade causes tests to fail. Either yoga didn't follow semver, or our tests are too strict.

@n1ru4l Changing the error code is a breaking change; does that mean Yoga doesn't follow semver?

In semver any breaking change (of an exposed API) requires a major increment, regardless of adoption rate. I'm asking for us to know whether we have to be careful in...

> If someone uses Object.entries on that object or maps over a TypeScript type that could also be considered a breaking change. In projects where a high level of stability...

There is a pending PR to refactor the error messages. Maybe it helps to merge that first?