[DSD-9664] injistackdev to injistackdev2

[gaganamadival]

Summary by CodeRabbit

• Chores
  • Updated service dependencies to the latest versions.

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

[coderabbitai]

Walkthrough

Updated the vidivi release manifest by replacing a single PMS API test image reference with two new Inji verification service image entries, both pointing to the develop branch from the injistackdev registry.

Changes

Cohort / File(s)	Summary
Manifest update release/vidivi/images.txt	Replaced mosipdev2/apitest-pms:release-1.3.x entry with injistackdev/inji-verify-service:develop and injistackdev/inji-verify-ui:develop entries

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• [DSD-9636] Image transfer from injistackdev to injistackdev2 #1523: Modifies the same manifest file, replacing a single image entry with the identical two image names (inji-verify-service and inji-verify-ui).
• [DSD-9652] injistackdev to injistackdev2 #1525: Updates the same manifest file to replace release-1.3.x references with injistackdev develop images.
• [DSD-9585] mosipdev2 to mosipqa #1511: Splits a single image entry into two separate entries for inji-verify-service and inji-verify-ui in the same manifest file.

Suggested reviewers

• Prafulrakhade

Poem

🐰 Two services hop where one did stand,
From ancient test to verify's grand brand,
The develop branch now takes the lead,
Injistackdev fulfills the need!
Hop, hop—the manifest's complete! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The PR title claims to change 'injistackdev to injistackdev2', but the actual changes replace 'mosipdev2' image entries with 'injistackdev' entries, which is inconsistent with the stated objective.	Update the PR title to accurately reflect the changes, such as 'DSD-9664 Replace mosipdev2 images with injistackdev images' or clarify the actual scope of changes.

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

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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

🤖 Fix all issues with AI agents

In `@release/vidivi/images.txt`:
- Around line 1-2: The image manifest still references the old registry and
mutable tags: update both occurrences of
injistackdev/inji-verify-service:develop and injistackdev/inji-verify-ui:develop
to the new registry injistackdev2 and replace the mutable "develop" tag with
immutable version identifiers (e.g.,
injistackdev2/inji-verify-service:develop-v1.0 or a specific semver/release tag
or digest) so the images are pinned for reproducible releases.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

# Check the file content
cat -n release/vidivi/images.txt

Repository: mosip/release-script

Length of output: 170

---

🏁 Script executed:

# Search for any PR or changelog context that mentions registry changes
rg "injistackdev|injistackdev2" --type txt --type md -A 2 -B 2

Repository: mosip/release-script

Length of output: 208

---

🏁 Script executed:

# Check if there are other image configuration files for context
fd -e txt -e md -e yaml -e yml | grep -i "image\|manifest\|release" | head -20

Repository: mosip/release-script

Length of output: 670

---

🏁 Script executed:

# Check the vidivi config and documentation
cat -n release/vidivi/config.yml

Repository: mosip/release-script

Length of output: 445

---

🏁 Script executed:

# Check README for context about this file
cat -n release/vidivi/README.md

Repository: mosip/release-script

Length of output: 16774

---

🏁 Script executed:

# Check git log for recent commits to this file
git log --oneline -10 release/vidivi/images.txt 2>/dev/null || echo "No git history available"

Repository: mosip/release-script

Length of output: 112

---

🏁 Script executed:

# Check the checks/images.txt for comparison to understand the pattern
cat -n release/checks/images.txt

Repository: mosip/release-script

Length of output: 3165

---

Update registry to injistackdev2 and replace mutable develop tags with immutable versions.

The commit message confirms the migration intent from injistackdev to injistackdev2, but the manifest still references injistackdev. Additionally, develop tags are mutable and break release reproducibility—use immutable version/digest tags instead (e.g., develop → a specific version like develop-v1.0 or release version).

🤖 Prompt for AI Agents

In `@release/vidivi/images.txt` around lines 1 - 2, The image manifest still
references the old registry and mutable tags: update both occurrences of
injistackdev/inji-verify-service:develop and injistackdev/inji-verify-ui:develop
to the new registry injistackdev2 and replace the mutable "develop" tag with
immutable version identifiers (e.g.,
injistackdev2/inji-verify-service:develop-v1.0 or a specific semver/release tag
or digest) so the images are pinned for reproducible releases.