fix: update jest to ^30.2.0 to fix installation failure

[space0bonzo]

Summary

• Updates jest dependency from ^30.0.4 to ^30.2.0
• Jest 30.0.4 was not available on npm registry during installation, causing No matching version found for jest@^30.0.4 error

Related Issue

Fixes bmad-code-org/BMAD-METHOD#1411

Test plan

• Run npx bmad-method install and select BMM module
• Verify dependencies install successfully

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Updated testing dependencies for improved development tooling.

---

Note: This release contains only internal maintenance updates with no changes to user-facing functionality.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Jest dependency updated from ^30.0.4 to ^30.2.0 in package.json. This resolves an installation error where the specified version does not exist; Jest releases jumped directly to 30.2.0, skipping the 30.0.4 version.

Changes

Cohort / File(s)	Summary
Dependency version bump package.json	Jest devDependency updated from ^30.0.4 to ^30.2.0 to match available release versions

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related issues

• #1411: Directly addresses the reported "No matching version found for jest@^30.0.4" installation error by updating to ^30.2.0, the actual available version from Jest's release cycle.

Poem

A hoppy fix for jest's release,
Now versions flow with perfect peace,
No more errors blocking the way,
Dependencies work again, hooray! 🐰✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title directly and concisely describes the main change: updating jest to ^30.2.0 to fix an installation failure, which matches the changeset.
Linked Issues check	✅ Passed	The PR updates jest from ^30.0.4 to ^30.2.0, directly addressing issue #1411's requirement to restore successful installation by requesting a valid Jest release available on npm.
Out of Scope Changes check	✅ Passed	The PR contains only a jest dependency version bump in package.json with no other unrelated or out-of-scope changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ 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.}