Skip to content

[DSD-9834] injistackdev to injistackdev2 - #1595

Merged
abhishek8shankar merged 1 commit into
mosip:release-1.2.0.1from
gaganamadival:release-1.2.0.1
Feb 24, 2026
Merged

[DSD-9834] injistackdev to injistackdev2#1595
abhishek8shankar merged 1 commit into
mosip:release-1.2.0.1from
gaganamadival:release-1.2.0.1

Conversation

@gaganamadival

@gaganamadival gaganamadival commented Feb 24, 2026

Copy link
Copy Markdown
Contributor

Summary by CodeRabbit

  • Chores
    • Updated deployment infrastructure configuration to reference new services.

Signed-off-by: gaganamadival <94885434+gaganamadival@users.noreply.github.com>
@coderabbitai

coderabbitai Bot commented Feb 24, 2026

Copy link
Copy Markdown

Walkthrough

Updated the Vidivi release image manifest by replacing three mosipdev entries (pmp-ui-v2, partner-management-service, policy-management-service) with two injistackdev entries (inji-web, mimoto).

Changes

Cohort / File(s) Summary
Release Manifest Update
release/vidivi/images.txt
Removed three mosipdev image entries and added two injistackdev image entries to the release configuration.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

  • [DSD-9652] injistackdev to injistackdev2 #1525: Modifies the same release manifest file by removing identical mosipdev entries and adding different injistackdev image entries, indicating parallel or coordinated updates to the release configuration.

Poem

🐰 Hippity-hop through the manifest we go,
Trading old images for new ones below,
Mosipdev out, injistackdev in,
Fresh dependencies to begin! 📦✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Title check ⚠️ Warning The PR title mentions 'injistackdev to injistackdev2' but the actual changes replace mosipdev entries with injistackdev entries, not injistackdev2. Update the title to accurately reflect the changes, such as 'DSD-9834 Replace mosipdev with injistackdev entries' or 'DSD-9834 Update image references to injistackdev'.
✅ 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.

✨ 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

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@release/vidivi/images.txt`:
- Around line 1-2: The two image entries "injistackdev/inji-web:develop develop"
and "injistackdev/mimoto:develop develop" use the registry name injistackdev but
the PR title indicates the registry should be injistackdev2; update those image
references to use injistackdev2 (i.e., change the prefix injistackdev to
injistackdev2 for the "inji-web" and "mimoto" entries) so the registry names
match the intended target.

ℹ️ Review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 726d67f and 3663224.

📒 Files selected for processing (1)
  • release/vidivi/images.txt

Comment thread release/vidivi/images.txt
Comment on lines +1 to +2
injistackdev/inji-web:develop develop
injistackdev/mimoto:develop develop

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Registry name mismatch with PR title — verify injistackdev vs injistackdev2.

The PR title states "injistackdev to injistackdev2", implying the intended registry is injistackdev2, but both added entries use injistackdev. If the goal was to point to injistackdev2, these lines are incorrect.

🔧 Proposed fix if `injistackdev2` was the intended registry
-injistackdev/inji-web:develop develop
-injistackdev/mimoto:develop develop
+injistackdev2/inji-web:develop develop
+injistackdev2/mimoto:develop develop
📝 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
injistackdev/inji-web:develop develop
injistackdev/mimoto:develop develop
injistackdev2/inji-web:develop develop
injistackdev2/mimoto:develop develop
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@release/vidivi/images.txt` around lines 1 - 2, The two image entries
"injistackdev/inji-web:develop develop" and "injistackdev/mimoto:develop
develop" use the registry name injistackdev but the PR title indicates the
registry should be injistackdev2; update those image references to use
injistackdev2 (i.e., change the prefix injistackdev to injistackdev2 for the
"inji-web" and "mimoto" entries) so the registry names match the intended
target.

@abhishek8shankar
abhishek8shankar merged commit 4317e51 into mosip:release-1.2.0.1 Feb 24, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants