Skip to content

[DSD-9638] injistackdev to injistackdev2 - #1522

Merged
Prafulrakhade merged 2 commits into
mosip:release-1.2.0.1from
gaganamadival:release-1.2.0.1
Jan 19, 2026
Merged

[DSD-9638] injistackdev to injistackdev2 #1522
Prafulrakhade merged 2 commits into
mosip:release-1.2.0.1from
gaganamadival:release-1.2.0.1

Conversation

@gaganamadival

@gaganamadival gaganamadival commented Jan 19, 2026

Copy link
Copy Markdown
Contributor

Summary by CodeRabbit

  • Chores
    • Updated container image reference in deployment configuration files to ensure the correct image is used for application deployment.

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

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

coderabbitai Bot commented Jan 19, 2026

Copy link
Copy Markdown

Walkthrough

Updated a container image reference in the release configuration file, replacing injistackdev/inji-certify-with-plugins:develop with injistackdev/apitest-inji-certify:develop.

Changes

Cohort / File(s) Summary
Release Configuration
release/vidivi/images.txt
Replaced inji-certify container image from injistackdev/inji-certify-with-plugins:develop to injistackdev/apitest-inji-certify:develop

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Suggested reviewers

  • Prafulrakhade

Poem

🐰 A docker image hops away,

New reference saves the day,

From plugins old to apitest new,

One little change, one line or two! 🐳

🚥 Pre-merge checks | ✅ 2 | ❌ 1
❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Title check ⚠️ Warning The title mentions 'injistackdev to injistackdev2' but the actual change replaces 'injistackdev/inji-certify-with-plugins' with 'injistackdev/apitest-inji-certify', which is a different image reference change. Update the title to accurately reflect the actual change, such as 'DSD-9638 Update Docker image reference from inji-certify-with-plugins to apitest-inji-certify' to better describe what was changed.
✅ 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

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

@Prafulrakhade
Prafulrakhade merged commit e0e40f0 into mosip:release-1.2.0.1 Jan 19, 2026
1 of 2 checks passed

@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

🤖 Fix all issues with AI agents
In `@release/vidivi/images.txt`:
- Line 1: The image reference currently uses
injistackdev/apitest-inji-certify:develop which is inconsistent with the PR
intent; update the registry/namespace to injistackdev2 and replace the develop
tag with a stable release tag (e.g., change
injistackdev/apitest-inji-certify:develop to
injistackdev2/apitest-inji-certify:<stable-version>) ensuring the new
<stable-version> is the proper semantic or released version for production.

Comment thread release/vidivi/images.txt
@@ -1 +1 @@
injistackdev/inji-certify-with-plugins:develop develop
injistackdev/apitest-inji-certify: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 | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Check if injistackdev2 registry exists and find other references to these registries

# Search for other occurrences of injistackdev or injistackdev2 in the repository
echo "=== Searching for injistackdev references ==="
rg -n "injistackdev" --type txt

echo -e "\n=== Searching for injistackdev2 references ==="
rg -n "injistackdev2" --type txt

echo -e "\n=== Searching for inji-certify related images ==="
rg -n "inji-certify" --type txt

# Also check git log/commit messages for the PR title
echo -e "\n=== Checking git history for DSD-9638 ==="
git log --all --oneline | grep -i "DSD-9638\|injistackdev2" | head -20

Repository: mosip/release-script

Length of output: 515


Critical: PR title and actual changes are inconsistent.

The git commit message indicates changing "injistackdev to injistackdev2", but the image reference still uses injistackdev as the registry/namespace. Additionally, the develop tag is being used in a release configuration file, which is typically inappropriate for production releases.

Please fix:

  1. Update the registry/namespace to injistackdev2 as indicated in the PR intent
  2. Replace the develop tag with a stable version tag appropriate for release configurations
🤖 Prompt for AI Agents
In `@release/vidivi/images.txt` at line 1, The image reference currently uses
injistackdev/apitest-inji-certify:develop which is inconsistent with the PR
intent; update the registry/namespace to injistackdev2 and replace the develop
tag with a stable release tag (e.g., change
injistackdev/apitest-inji-certify:develop to
injistackdev2/apitest-inji-certify:<stable-version>) ensuring the new
<stable-version> is the proper semantic or released version for production.

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