Skip to content

DSD-9251 - #1393

Merged
Prafulrakhade merged 1 commit into
mosip:release-1.2.0.1from
dhanendra06:MOSIP-06
Nov 19, 2025
Merged

DSD-9251#1393
Prafulrakhade merged 1 commit into
mosip:release-1.2.0.1from
dhanendra06:MOSIP-06

Conversation

@dhanendra06

@dhanendra06 dhanendra06 commented Nov 19, 2025

Copy link
Copy Markdown
Contributor

Summary by CodeRabbit

  • Chores
    • Updated service image reference to a newer version.

Signed-off-by: Dhanendra Sahu <dhanendra.tech@gmail.com>
@coderabbitai

coderabbitai Bot commented Nov 19, 2025

Copy link
Copy Markdown

Walkthrough

A single container image reference in the release configuration file was updated, replacing the mosipdev2/apitest-inji-certify image with mosipdev/print and updating the version tag from 0.13.x to 1.3.x.

Changes

Cohort / File(s) Change Summary
Container Image References
release/vidivi/images.txt
Updated image reference from mosipdev2/apitest-inji-certify:release-0.13.x to mosipdev/print:release-1.3.x

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

  • Verify the new image reference (mosipdev/print:release-1.3.x) is valid and correctly versioned for the release
  • Confirm the repository and tag change align with release objectives

Possibly related PRs

Suggested reviewers

  • ckm007

Poem

🐰 A print job arrives in the release queue,
Old certify bundles bid their adieu,
From dev2 to dev, the images flow,
Version one-point-three steals the show! 📦✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Title check ⚠️ Warning The title 'DSD-9251' is a ticket identifier that does not describe the actual change made (replacing a Docker image reference in release/vidivi/images.txt). Replace the ticket ID with a descriptive title that summarizes the main change, such as 'Update Docker image reference in release/vidivi/images.txt' or 'Update vidivi Docker image to print:release-1.3.x'.
✅ 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

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

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c49f805 and c4fd181.

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

Comment thread release/vidivi/images.txt
@@ -1 +1 @@
mosipdev2/apitest-inji-certify:release-0.13.x 0.13.x
mosipdev/print:release-1.3.x 1.3.x

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

Verify the rationale and impact of this image replacement.

This change replaces the image entirely—from mosipdev2/apitest-inji-certify:release-0.13.x to mosipdev/print:release-1.3.x—which is a substantial change involving a different repository, organization, and version. This is not a routine version bump.

Before merging, confirm:

  1. Intentionality: Is this image swap intentional, or was the wrong image reference edited?
  2. Old image removal: Verify that mosipdev2/apitest-inji-certify is not still required elsewhere in the codebase or release artifacts.
  3. New image readiness: Ensure mosipdev/print:release-1.3.x exists, is properly tested, and is ready for production use in release-1.2.0.1.
  4. Rationale: Document why this specific image replacement is necessary in this release.

🏁 Script executed:

#!/bin/bash
# Description: Verify old image reference is not used elsewhere in the repository

echo "=== Checking for remaining references to old image ==="
rg -i "apitest-inji-certify" --type=txt --type=yaml --type=yml

echo -e "\n=== Checking for references to old org (mosipdev2) in images ==="
rg "mosipdev2" --type=txt --type=yaml --type=yml | grep -i image || echo "No other mosipdev2 references found"

echo -e "\n=== Listing all image.txt or image-related config files ==="
fd -e txt -e yaml -e yml | grep -i image | head -20

Length of output: 325


🏁 Script executed:

#!/bin/bash
# Description: Verify old image references with corrected rg syntax and examine image files

echo "=== Checking for remaining references to old image (corrected) ==="
rg -i "apitest-inji-certify" || echo "No references to apitest-inji-certify found"

echo -e "\n=== Checking for references to old org (mosipdev2) ==="
rg "mosipdev2" || echo "No references to mosipdev2 found"

echo -e "\n=== Content of release/vidivi/images.txt ==="
cat release/vidivi/images.txt

echo -e "\n=== Content of release/checks/images.txt ==="
cat release/checks/images.txt

echo -e "\n=== Searching for any references to 'print:release' image ==="
rg "print:release" || echo "No other print:release references found"

echo -e "\n=== Searching for version 1.3.x references ==="
rg "1\.3\.x" || echo "No 1.3.x references found"

Length of output: 9098


🏁 Script executed:

#!/bin/bash
# Description: Understand purpose of vidivi/images.txt and context of this change

echo "=== Content of release/vidivi/README.md ==="
cat release/vidivi/README.md 2>/dev/null || echo "README.md not found"

echo -e "\n=== Checking for any documentation about images.txt purpose ==="
fd -e md | xargs grep -l "images.txt" 2>/dev/null || echo "No docs mention images.txt"

echo -e "\n=== Looking for configuration or scripts that use vidivi/images.txt ==="
rg "vidivi.*images" || echo "No references to vidivi images.txt usage"

echo -e "\n=== Checking transfer_report.md for full context ==="
cat release/vidivi/transfer_report.md 2>/dev/null | head -50

echo -e "\n=== Search for print service references in production ==="
rg "print" release/checks/images.txt

Length of output: 15110


Version mismatch detected: vidivi will transfer image version 1.3.x, but production release expects 1.2.0.

This change updates vidivi/images.txt to transfer mosipdev/print:release-1.3.x to the staging registry. However, the production configuration (release/checks/images.txt) specifies mosipid/print:1.2.0 for release-1.2.0.1. This version mismatch will cause the wrong image to be deployed during the release.

The transfer report from Nov 18 shows the previous image was just successfully staged, and this configuration update will cause the next vidivi run to transfer an incompatible version (1.3.x instead of 1.2.0).

Correct release/vidivi/images.txt to use mosipdev/print:1.2.0 to align with the production image list, or clarify why a higher version should be used for this release.

🤖 Prompt for AI Agents
In release/vidivi/images.txt around lines 1 to 1, the image entry was changed to
mosipdev/print:release-1.3.x which mismatches production's expected
mosipid/print:1.2.0; revert or update this entry to the correct image tag by
replacing mosipdev/print:release-1.3.x with mosipdev/print:1.2.0 (or, if this
release intentionally requires 1.3.x, add a clear justification comment and
coordinate updating release/checks/images.txt and the deployment config to
accept mosipdev/print:1.3.x so the vidivi transfer and production lists remain
aligned).

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