[DSD-9279] image move from dev2 to qa

[gaganamadival]

Summary by CodeRabbit

• Chores
  • Updated container image repository reference in release configuration.

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

[coderabbitai]

Walkthrough

Updated a Docker image reference in release/vidivi/images.txt from the mosipdev namespace to mosipdev2, and normalized the version tag by removing the "release-" prefix from the secondary tag identifier.

Changes

Cohort / File(s)	Summary
Docker image namespace and tag update release/vidivi/images.txt	Changed mosipdev/uitest-verify:release-0.15.x release-0.15.x to mosipdev2/uitest-verify:release-0.15.x 0.15.x, migrating repository namespace and normalizing version tag format.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• [DSD-9235] Image transfer from dev2 to qa. #1388: Makes the same code-level change pattern in release/vidivi/images.txt—switching image namespace from mosipdev to mosipdev2 and normalizing the second tag.
• [DSD-9235] IMage transfe from dev to dev2 . #1387: Modifies release/vidivi/images.txt to transfer image entries from the mosipdev namespace to mosipdev2 and adjust tags.
• [DSD-9263] mosipdev2 to mosipqa #1392: Updates image repository namespaces from mosipdev to mosipdev2 in the same file with the same kind of image reference change.

Poem

🐰 From mosipdev to mosipdev2 it hops,

The image namespace gracefully swaps,

Release tags trimmed with a careful snip,

Configuration flows on a streamlined trip! 🚀

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title indicates moving images from dev2 to qa, but the actual change shows the repository namespace changed from mosipdev to mosipdev2, which contradicts the stated direction.	Revise the title to accurately reflect the actual change: consider 'DSD-9279 image move from dev to dev2' or clarify the intended direction if the title is correct and the change needs adjustment.

✅ 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 2a752a0 and 7ad03d4.

📒 Files selected for processing (1)

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

🔇 Additional comments (1)

release/vidivi/images.txt (1)

1-1: No issues found; change is properly scoped and follows established patterns.

Verification confirms: (1) release/vidivi/images.txt is the only file containing this image reference—no additional updates needed; (2) the format <image>:<tag> <version> matches patterns already used in release/checks/images.txt; (3) registry isolation is intentional (mosipdev2 for test images, mosipid for production) and properly maintained across the codebase.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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