fix: update mongodb fcv to 6

[wyattwalter]

Description

Looks like when the embedded MongoDB version was last updated, the feature compatibility version parameter was not updated. This means that any instances that started on 1.66 or less using the embedded MongoDB didn't have their compatibility version updated. This'll make the jump to 7.x harder as we need to ensure this is at least 6 in those scenarios. Getting this in place now.

Fixes #Issue Number
or
Fixes Issue URL

Warning

If no issue exists, please create an issue first, and check with the maintainers if the issue is valid.

Automation

/ok-to-test tags=""

🔍 Cypress test results

Caution

If you modify the content in this section, you are likely to disrupt the CI result for your PR.

Communication

Should the DevRel and Marketing teams inform users about this change?

• Yes
• No

Summary by CodeRabbit

• Chores
  • Updated MongoDB feature compatibility from version 5.x to 6.x in deployment configuration.

[coderabbitai]

Walkthrough

The MongoDB feature compatibility version was upgraded from 5.x to 6.x in the fixer script. Version comparison thresholds and log messages were updated accordingly to reflect the new target version while maintaining existing control flow logic.

Changes

Cohort / File(s)	Summary
MongoDB Version Upgrade deploy/docker/fs/opt/appsmith/mongodb-fixer.sh	Updated feature flag version (FFV) check from 5.0 to 6.0 and adjusted conditional threshold from < 5 to < 6. Log message updated to reflect new version target.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🚀 From five to six, the MongoDB sails,
A version bump that never fails,
Fixer scripts now set their sight,
On compatibility, shining bright! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description provides context about the change and its rationale, but the 'Fixes' field contains only a placeholder without an actual issue reference.	Replace the placeholder in the 'Fixes' field with an actual issue number or URL to properly link this PR to the issue it addresses.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main change: updating MongoDB feature compatibility version (FCV) to version 6.
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 docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch ww-mongodb-set-compatibility-version

---

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

[subrata71]

Will this change have any impact on existing customer data for instances that were previously running MongoDB 5.x or any version prior to 6.x?

[wyattwalter]

It'll just set the compatibility level to 6 (we're running 6 now) so that we can hop to 7. It does mean that you can't start up an older version of MongoDB using the data directory. But that would also not work once Appsmith starts anyway, so it doesn't matter.