[DSD-9202] move image fom dev to dev2

[gaganamadival]

Summary by CodeRabbit

• Chores
  • Updated deployment image reference to a new version and repository.

[coderabbitai]

Walkthrough

A Docker image reference in the release configuration is updated from mosipdev/esignet-with-plugins:release-1.7.x to mosipdev/inji-certify-with-plugins:release-0.13.x, replacing the esignet image with an inji-certify variant.

Changes

Cohort / File(s)	Summary
Release Configuration Update release/vidivi/images.txt	Replaced esignet-with-plugins image reference (1.7.x tag) with inji-certify-with-plugins image reference (0.13.x tag)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• [DSD-9180] image moved from dev2 to qa #1355: Modifies the same release/vidivi/images.txt entry and removes the esignet-with-plugins:release-1.7.x image that is being replaced.
• [DSD-9196] Image transfer from mosipdev2 to mosipqa #1361: Updates release/vidivi/images.txt with the same inji-certify-with-plugins:release-0.13.x image target reference.
• [DSD-9201] mosipdev to mosipqa #1362: Modifies release/vidivi/images.txt and updates the identical inji-certify-with-plugins image entry.

Poem

🐰 A hop, a skip, through images we glide,
From esignet's past to certify with pride,
One-point-seven fades, zero-thirteen takes flight,
Release notes updated, all versioned just right! 🚀

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title contains a typo ('fom' instead of 'from') and is vague about the actual change - it doesn't clearly indicate that a Docker image reference is being replaced from esignet to inji-certify.	Clarify the title to describe the specific change more precisely, e.g., 'Replace esignet image with inji-certify in release images' and fix the typo 'fom' to 'from'.

✅ 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

---

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

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 20c4744 and 7733dfa.

📒 Files selected for processing (1)

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

🔇 Additional comments (1)

release/vidivi/images.txt (1)

1-1: The Docker image is valid, accessible, and confirmed to be active.

The verification confirms that mosipdev/inji-certify-with-plugins:release-0.13.x exists on Docker Hub as a public image with both amd64 and arm64 architectures. The image was last pushed on Nov 11 and pulled today (Nov 12), indicating recent use. The file addition aligns with the established vidivi image transfer workflow shown in the repository's release process for Docker image promotions.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Fix format inconsistency in the tag version field.

The second field (tag version) breaks the established pattern. Based on the AI summary, the previous line used format image:release-1.7.x 1.7.x (version only in the second field), but the new line uses image:release-0.13.x release-0.13.x (full tag with prefix in the second field).

Apply this diff to align with the established format:

-mosipdev/inji-certify-with-plugins:release-0.13.x release-0.13.x
+mosipdev/inji-certify-with-plugins:release-0.13.x 0.13.x

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	mosipdev/inji-certify-with-plugins:release-0.13.x release-0.13.x
	mosipdev/inji-certify-with-plugins:release-0.13.x 0.13.x

🤖 Prompt for AI Agents

In release/vidivi/images.txt around lines 1 to 1, the tag version field repeats
the full tag instead of using only the version suffix; change the second field
from "release-0.13.x" to just "0.13.x" so the line becomes
"mosipdev/inji-certify-with-plugins:release-0.13.x 0.13.x", keeping the image
reference intact and aligning with the established pattern.