Manuel

The thing is that we wouldn't be able to upgrade the JS SDK in Parse Server until December 2025 if we merged this. So we can't really merge this so...

The Parse JS SDK is a dependency of Parse Sever.

The difference is that the Parse JS SDK is a fully exposed API in Cloud Code, not merely a "hidden" dependency (which we want to [change](https://github.com/parse-community/parse-server/issues/8787)). The "hidden" dependencies are...

Which one of these are breaking and are there interdependencies? If only this crypto PR is breaking, then we can do a 7.0.0 release without waiting for the other ones....

@dplewis Would love to merge this as well; to make this easy to understand for developers, could you take a look at my questions at https://github.com/parse-community/Parse-SDK-JS/pull/2501#pullrequestreview-3068449899?

This is a different thing. It's an attempt (wip) to change the CI to install a specific version of Parse Server, then install the current JS SDK in Parse Server...

> I'd rather keep the current way of release the SDK then open a PR on the server and see if it breaks. What happens if the Parse Server test...

> Besides Parse.Error, Parse._encode, Parse._decode what else does Parse Server use internally that could potentially break it? Well, for example these. I'm fine with leaving as is, but I'm afraid...

Sounds like a perfect case for a puppeteer test!

I think you have the wrong base for this PR, the base branch does not seem to be up-to-date, hence the file conflicts. Also, in https://github.com/parse-community/Parse-SDK-Android/pull/1216 I removed ``` tasks.withType(Test)...