fix: Cannot connect to server with error invalid header name

[mtrezza]

New Pull Request Checklist

• I am not disclosing a vulnerability.
• I am creating this PR in reference to an issue.

Issue Description

Cannot connect to server with error:

Server not reachable: Failed to execute 'has' on 'Headers': Invalid name.

Approach

Bug should have been fixed in Parse JS SDK 7.0.2 with parse-community/Parse-SDK-JS#2754.

Summary by CodeRabbit

• Chores
  • Updated project dependencies to maintain stability and compatibility.

[parse-github-assistant]

🚀 Thanks for opening this pull request! We appreciate your effort in improving the project. Please let us know once your pull request is ready for review.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request updates package.json dependencies by bumping the parse package from version 7.0.1 to 7.0.2 and reordering the express-session entry within the dependencies object.

Changes

Cohort / File(s)	Summary
Dependency updates package.json	Updated parse from 7.0.1 to 7.0.2; reordered express-session 1.18.2 within dependencies

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• fix: Security upgrade parse from 3.5.1 to 7.0.1 #3003: Upgrades the parse dependency in the same package.json, with this PR continuing a further version bump (7.0.1 → 7.0.2).

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The PR description is incomplete when compared to the required template. While it includes the New Pull Request Checklist, Issue Description, and Approach sections, it is missing two key components: the "Closes:" field to link the PR to an issue, and the entire TODOs before merging section. The template explicitly requires a "Closes: FILL_THIS_OUT" entry in the Issue Description, and the TODOs section—which helps track prerequisites like testing and documentation—is entirely absent. This represents a significant gap in required information, particularly the issue tracking linkage.	The author should add the missing "Closes:" field to link this PR to the relevant issue and include the TODOs section with checkboxes for "Add tests" and "Add changes to documentation" (or explicitly delete them if not applicable with justification). These additions will ensure the description matches the repository's template and provides complete information for reviewers to understand what work remains before merging.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The PR title "fix: Cannot connect to server with error invalid header name" describes the bug being fixed rather than the specific change being made. The actual changeset updates the parse dependency from 7.0.1 to 7.0.2 in package.json, which is the primary action taken in this PR. While the title is related to the purpose and outcome of the PR (it addresses what problem is being solved), it does not clearly describe the main change itself. However, the title is not misleading or off-topic—it correctly identifies the issue that the parse upgrade resolves, making it partially related to the changeset.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[parseplatformorg]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[uffizzi-cloud]

Uffizzi Ephemeral Environment deployment-65695

⌚ Updated Oct 25, 2025, 10:02 UTC

☁️ https://app.uffizzi.com/github.com/parse-community/parse-dashboard/pull/3006

📄 View Application Logs etc.

What is Uffizzi? Learn more

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

package.json (1)

49-49: Clarify the purpose of express-session repositioning.

The express-session entry appears to have been repositioned within the dependencies object (line 49). While the version remains "1.18.2", clarify whether this reordering is:

• An intentional alphabetical sort for consistency
• A result of dependency management tooling
• Part of a broader formatting update

This appears to be a non-functional change, but documenting the intent would clarify the PR's scope.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 924085b and 5235fb7.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• package.json (2 hunks)

🔇 Additional comments (2)

package.json (2)

60-60: Based on my search attempts, I was unable to access the specific release notes for Parse SDK version 7.0.2 directly through web search. The GitHub releases page for parse-community/Parse-SDK-JS appears to have loading issues, which prevented retrieval of detailed changelog information for the 7.0.1 → 7.0.2 transition.

Given these limitations, here is the rewritten review comment:

---

Verify parse 7.0.2 changelog for compatibility and behavioral changes.

The version bump from parse 7.0.1 to 7.0.2 is a patch upgrade. While Snyk confirmed zero vulnerabilities, manually verify the official release notes at https://github.com/parse-community/Parse-SDK-JS/releases to ensure there are no breaking changes, behavioral differences, or API updates that could affect integration.

---

---

1-179: PR template concerns are outside the scope of code review; verify locally before merging.

The review addresses PR checklist items (unfilled "Closes" field, unchecked TODOs) which are metadata in the PR description, not reflected in the code snippet provided (package.json). The code change itself—updating parse from prior version to 7.0.2—is present and compatible with existing version-checking logic.

To proceed:

1. Complete PR description checklist fields manually
2. Run npm test locally (cannot execute in sandbox)
3. Verify any parse SDK v7.0.2 breaking changes against your application code (codebase has no SDK-level version conditionals)

[parseplatformorg]

🎉 This change has been released in version 8.0.0-alpha.2