[DSD-9263] mosipdev to mosipdev2

[SwapnilWorks-Devops]

Summary by CodeRabbit

• Chores
  • Updated component image references in the release configuration. Two previously included image entries have been replaced with a new image entry, reflecting changes to the deployment composition for this release.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This change updates the Docker image references in the release configuration file, removing two legacy image entries tied to release-1.3.x and introducing a new apitest-inji-certify image for release-0.13.x.

Changes

Cohort / File(s)	Summary
Release image reference update release/vidivi/images.txt	Replaced mosipdev/registration-client:release-1.3.x and mosipdev/commons-packet-service:release-1.3.x with mosipdev/apitest-inji-certify:release-0.13.x

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• [DSD-9190] mosipdev to mosipqa #1356: Modifies the same release/vidivi/images.txt file to prefix image entries with mosipdev/
• [DSD-9246] mosipdev to mosipdev2 #1380: Updates the same file and introduces the mosipdev/apitest-inji-certify image reference
• [DSD-9196] Image transfer from mosipdev2 to mosipqa #1361: Consolidates multiple image entries into a single inji-certify image at release-0.13.x in the same file

Poem

🐰 Two old images fade away,
Release one-three had their day,
Now apitest-inji steps in bright,
Point-thirteen shines with new delight!
Docker dreams in config files—
Simple swaps that spark smiles! ✨

✨ 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 ee7e93c and 5f24302.

📒 Files selected for processing (1)

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

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