[DSD-9279] move images from dev to dev2

[gaganamadival]

Summary by CodeRabbit

• Chores
  • Updated release configuration with a new service image entry for version 0.15.x, modifying the component set used in the release workflow.

[coderabbitai]

Walkthrough

Three develop-tagged image entries for package management services are replaced with a single release-tagged uitest-verify image entry in the Vidivi release manifest file.

Changes

Cohort / File(s)	Change Summary
Vidivi Release Manifest release/vidivi/images.txt	Removed three mosipdev image entries (pmp-ui-v2, partner-management-service, policy-management-service) all tagged develop, and added one mosipdev/uitest-verify:release-0.15.x entry

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Single manifest file with straightforward image entry replacement
• No logic or functional changes

Possibly related PRs

• [DSD-9238] mosipdev2 to mosipqa #1389: Also replaces image entries in the same manifest file with uitest-verify:release-0.15.x image.
• [DSD-9231] Image transfer from dev to dev2 . #1370: Similar manifest update pattern—removes multiple image lines and adds a single replacement entry to release/vidivi/images.txt.
• [DSD-9235] IMage transfe from dev to dev2 . #1387: Removes multiple mosipdev image entries and replaces them with a single new mosipdev image line in the same file.

Poem

🐰 Three images hop away so fast,
Develop tags belong to the past,
One new uitest-verify takes the stage,
Release-0.15.x turns the page! 📦✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title mentions moving images 'from dev to dev2', but the actual changes show removing dev-related images and adding a release-tagged image, which doesn't align with a 'dev to dev2' migration.	Update the title to accurately describe the change, such as 'DSD-9279 Replace dev images with release-0.15.x tagged image' or similar, reflecting the actual modifications made to the image entries.

✅ 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 08379ed and 0c4fa7b.

📒 Files selected for processing (1)

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

🔇 Additional comments (1)

release/vidivi/images.txt (1)

1-1: Verify: PR title mismatch and functional impact of removing three service images.

The PR title states "move images from dev to dev2," but the change actually:

• Removes three :develop-tagged service images (pmp-ui-v2, partner-management-service, policy-management-service)
• Replaces them with a single :release-0.15.x-tagged test/verify image

This is a significant functional change, not a dev→dev2 relocation. Confirm that:

1. The PR title/objective accurately describes this change
2. Removing the three service images is intentional and won't break the Vidivi release workflow
3. The file should contain only this single image entry

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