Upgrade to latest Parse SDK breaks test

[mtrezza]

trafficstars

New Issue Checklist

• [x] I am not disclosing a vulnerability.
• [x] I am not just asking a question.
• [x] I have searched through existing issues.
• [x] I can reproduce the issue with the latest version of Parse Server.

Issue Description

Upgrading to latest Parse SDK (4.3.1 as of writing) breaks the test:

1. Security Advisory GHSA-8w3j-g983-8jh5 should validate credentials first and check if account already linked afterwards ()

• Expected 208 to equal 206.

The test specifically expects 206 instead of 208 (as commented in the test), so it doesn't seem to be a deliberate change but rather a bug.

Steps to reproduce

See https://github.com/parse-community/parse-server/pull/8816.

Actual Outcome

Test fails.

Expected Outcome

Test passes.

[parse-github-assistant[bot]]

Thanks for opening this issue!

• 🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

[mtrezza]

Thanks to @dblythy this issue can be closed with https://github.com/parse-community/parse-server/pull/9022.