fix: Install the latest Parse Server version in bootstrap.sh

[dblythy]

Closes #8513

bootstrap.sh scaffolded a package.json that hardcoded "parse-server": "^3.9.0", so anyone following the getting-started guide ended up installing a 6-year-old v3 (current is 9.x).

Rather than bumping the pin to a new hardcoded version - which would just go stale again in a year - this drops the version from the generated package.json and installs parse-server at install time (npm install parse-server). npm pins whatever is current, so the script is self-healing and never needs a version bump again.

Verified end to end: running the script now generates a package.json pinned to the current release (^9.9.0) and installs a v9 binary.

Summary by CodeRabbit

• Chores
  • Updated the project setup flow so the server package is installed during installation instead of being prefilled in the generated dependency list.
  • Removed the fixed version constraint from the default package template, making setup more flexible.

[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.

Tip

• Keep pull requests small. Large PRs will be rejected. Break complex features into smaller, incremental PRs.
• Use Test Driven Development. Write failing tests before implementing functionality. Ensure tests pass.
• Group code into logical blocks. Add a short comment before each block to explain its purpose.
• We offer conceptual guidance. Coding is up to you. PRs must be merge-ready for human review.
• Our review focuses on concept, not quality. PRs with code issues will be rejected. Use an AI agent.
• Human review time is precious. Avoid review ping-pong. Inspect and test your AI-generated code.

Note

Please respond to review comments from AI agents just like you would to comments from a human reviewer. Let the reviewer resolve their own comments, unless they have reviewed and accepted your commit, or agreed with your explanation for why the feedback was incorrect.

Caution

Pull requests must be written using an AI agent with human supervision. Pull requests written entirely by a human will likely be rejected, because of lower code quality, higher review effort and the higher risk of introducing bugs. Please note that AI review comments on this pull request alone do not satisfy this requirement. Our CI and AI review are safeguards, not development tools. If many issues are flagged, rethink your development approach. Invest more effort in planning and design rather than using review cycles to fix low-quality code.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: f594f314-6939-4138-ba29-dd0d35495e8d

📥 Commits

Reviewing files that changed from the base of the PR and between 7e9d53a and a39b24c.

📒 Files selected for processing (1)

• bootstrap.sh

---

📝 Walkthrough

Walkthrough

The bootstrap.sh script is modified so the generated package.json template no longer contains a pinned parse-server dependency (now an empty dependencies object), and the npm install command explicitly installs parse-server instead of installing from package.json.

Changes

Bootstrap Install Fix

Layer / File(s)	Summary
Remove pinned version and update install command bootstrap.sh	Template package.json's dependencies object is now empty instead of pinning parse-server to a fixed version, and the npm install step is changed to explicitly run npm install parse-server -s instead of npm install -s.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Related issues: Addresses outdated parse-server installations caused by bootstrap.sh pinning an old version (#8513).

Suggested labels: bug, bootstrap

Suggested reviewers: dblythy, mtrezza

_{🐰 A pin removed, a version freed, / now bootstrap grabs what's truly needed. / No more stuck at three-point-nine, / latest parse-server, right on time. 🥕}

🚥 Pre-merge checks | ✅ 7

✅ Passed checks (7 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title uses the required fix: prefix and accurately describes the bootstrap.sh Parse Server version change.
Description check	✅ Passed	The description covers the issue and approach, though it omits the template's Tasks checklist and section headings.
Linked Issues check	✅ Passed	The change removes the stale pinned version and installs Parse Server at setup time, matching #8513's request for the current release.
Out of Scope Changes check	✅ Passed	The only changed area is bootstrap.sh and it stays focused on the Parse Server install flow.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Security Check	✅ Passed	Only change is a static npm install parse-server; no new eval, shell injection, or other advisory-style vuln pattern is introduced.
Engage In Review Feedback	✅ Passed	PR #10556 shows “No reviews” and only bot comments, so there was no review feedback to ignore or resolve.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.66%. Comparing base (cce91e5) to head (a39b24c).
⚠️ Report is 1 commits behind head on alpha.

Additional details and impacted files

@@           Coverage Diff           @@
##            alpha   #10556   +/-   ##
=======================================
  Coverage   92.66%   92.66%           
=======================================
  Files         193      193           
  Lines       16981    16981           
  Branches      248      248           
=======================================
  Hits        15736    15736           
  Misses       1224     1224           
  Partials       21       21           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.