[DSD-9497] image move from dev to dev2

[gaganamadival]

Summary by CodeRabbit

• Chores
  • Updated image references in the release configuration to accurately reflect the current development status and overall project pipeline requirements. Removed one component's previous release version reference and added development version references for two additional components. These configuration updates help maintain proper alignment with active development, testing, and deployment infrastructure needs.

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

[coderabbitai]

Walkthrough

The PR updates the image registry file for the Vidivi release, removing a partner-onboarder entry and adding two new image references for inji-web and mimoto, both pointing to develop branches.

Changes

Cohort / File(s)	Summary
Image Registry Update release/vidivi/images.txt	Removed mosipdev/partner-onboarder:release-1.3.x 1.3.x; added mosipdev/inji-web:develop develop and mosipdev/mimoto:develop develop

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• [DSD-9403] mosipdev to mosipdev2 #1433: Both PRs modify the same file and add the identical two image entries (mosipdev/inji-web:develop and mosipdev/mimoto:develop)
• [DSD-9280] image move from dev to dev2 #1401: Both PRs modify release/vidivi/images.txt and update the same inji-web and mimoto image entries
• [DSD-9186]move images from dev2 to qa #1350: Both PRs perform the same operation—replacing a single image entry with two separate new entries in the registry file

Suggested reviewers

• Prafulrakhade

Poem

🐰 Registry entries hop and skip,
Old partner-onboarder takes a trip,
Inji-web and mimoto arrive with cheer,
Develop branches bloom so clear!
Images dance through the file so bright, ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title refers to moving images between environments (dev to dev2), which does not clearly match the actual change of updating image entries in the vidivi/images.txt file.	Update the title to accurately reflect the change, such as 'DSD-9497 Update vidivi image entries' or 'DSD-9497 Replace partner-onboarder with inji-web and mimoto images'.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

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

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 314239d and e0d4127.

📒 Files selected for processing (1)

• release/vidivi/images.txt (1 hunks)

🔇 Additional comments (1)

release/vidivi/images.txt (1)

1-2: Verify branch targeting aligns with PR intent and release requirements.

The PR title mentions moving images "from dev to dev2", but the provided entries reference develop branches instead of dev2. Additionally, using develop-branch images in a release version (1.2.0.1) warrants confirmation that this is intentional and appropriate for your deployment strategy.

Please clarify:

1. Is develop the intended target, or should this be dev2 per the PR title?
2. Are develop-branch images suitable for this release deployment, or should these reference stable release/main branches?

---

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