chore: docker-compose-local using old bitnami image

[KevLehman]

Proposed changes (including videos or screenshots)

Issue(s)

Steps to test or reproduce

Further comments

Summary by CodeRabbit

• Chores
  • Updated MongoDB service configuration for improved compatibility and stability.
  • Enabled MongoDB port accessibility through container configuration.

[dionisio-bot]

Looks like this PR is not ready to merge, because of the following issues:

• This PR is missing the required milestone or project

Please fix the issues and try again

If you have any trouble, please check the PR guidelines

[changeset-bot]

⚠️ No Changeset found

Latest commit: abc0af2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

The MongoDB service in the Docker Compose configuration was updated to use a different image registry (bitnamilegacy) with a specific version tag (7.0.1), and the MongoDB port was exposed.

Changes

Cohort / File(s)	Summary
Docker Compose Configuration docker-compose-local.yml	Updated MongoDB image from docker.io/bitnami/mongodb:7.0 to docker.io/bitnamilegacy/mongodb:7.0.1 and added port mapping 27017:27017 for the mongo service

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A mongo machine, so sleek and so fine,
Now bitnamilegacy, version seven-point-one!
The ports open wide—twenty-seven-oh-one-seven—
This little config change feels just like heaven! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
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 (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The pull request title "chore: docker-compose-local using old bitnami image" accurately describes the main change in the changeset. The PR modifies the docker-compose-local.yml file by updating the MongoDB image from the standard bitnami variant to the bitnamilegacy variant (specifically from bitnami/mongodb:7.0 to bitnamilegacy/mongodb:7.0.1), which is directly related to what the title conveys. The title is specific about the file affected and the primary component being changed, making it clear to reviewers what the PR addresses. While the PR also includes a secondary change (adding port mapping), the title appropriately focuses on the most significant change without unnecessary details or vague terminology.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/local-compose

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Jira integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between d075db2 and abc0af2.

📒 Files selected for processing (1)

• docker-compose-local.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: 📦 Build Packages
• GitHub Check: CodeQL-Build
• GitHub Check: CodeQL-Build

🔇 Additional comments (3)

docker-compose-local.yml (3)

151-152: LGTM – Port exposure is appropriate for local development.

Exposing port 27017 is a reasonable addition for local development to allow direct access to MongoDB from the host machine.

---

148-149: Update the TODO comment and clarify the situation—the Bitnami deprecation deadline has passed.

After evaluating community feedback, Bitnami postponed the deletion of the bitnami catalog until September 29th, which has now passed. Since today is October 24, 2025, versioned images have been moved to bitnamilegacy, which will receive no further updates or support and should only be used for temporary migration purposes. The change to bitnamilegacy/mongodb:7.0.1 is now necessary rather than optional.

Update the TODO comment to reflect current status:

  mongo:
+   # Bitnami moved versioned images to bitnamilegacy (deadline: Sept 29, 2025)
+   # For local dev only; not for production. Upgrade or use managed MongoDB for long-term solutions.
+   # Ref: https://github.com/bitnami/charts/issues/35164
    image: docker.io/bitnamilegacy/mongodb:7.0.1
    restart: on-failure

---

1-173: Add PR description explaining deprecation and migration plan.

Bitnami began deprecating its public Docker Hub catalog on August 28, 2025, moving most versioned images to the "Bitnami Legacy" repository. The switch to docker.io/bitnamilegacy/mongodb:7.0.1 is necessary and appropriate. However, bitnamilegacy images are archived and will not receive updates, security patches, or ongoing maintenance.

The PR description must document:

• Why this change is necessary (Bitnami catalog deprecation)
• Timeline for migrating to a maintained alternative (official MongoDB image or Bitnami Secure Images)
• Any impact on development workflows during the transition

This prevents leaving the codebase on an unmaintained registry long-term.

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 67.61%. Comparing base (d075db2) to head (abc0af2).
⚠️ Report is 1 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop   #37297      +/-   ##
===========================================
- Coverage    67.64%   67.61%   -0.03%     
===========================================
  Files         3338     3338              
  Lines       113721   113721              
  Branches     20663    20663              
===========================================
- Hits         76923    76895      -28     
- Misses       34126    34143      +17     
- Partials      2672     2683      +11     

Flag	Coverage Δ
e2e	57.40% <ø> (-0.07%)	⬇️
unit	71.60% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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