Skip to content

[DSD-9452] mosipdev2 to mosipqa - #1464

Merged
abhishek8shankar merged 1 commit into
mosip:release-1.2.0.1from
SwapnilWorks-Devops:release-1.2.0.1
Dec 10, 2025
Merged

[DSD-9452] mosipdev2 to mosipqa#1464
abhishek8shankar merged 1 commit into
mosip:release-1.2.0.1from
SwapnilWorks-Devops:release-1.2.0.1

Conversation

@SwapnilWorks-Devops

@SwapnilWorks-Devops SwapnilWorks-Devops commented Dec 10, 2025

Copy link
Copy Markdown
Contributor

Summary by CodeRabbit

Release Notes

  • Chores
    • Updated image registry references and adjusted version tag format for consistency.

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

Signed-off-by: Swapnil <swapnil.mohanty@technoforte.co.in>
@coderabbitai

coderabbitai Bot commented Dec 10, 2025

Copy link
Copy Markdown

Walkthrough

Updated image registry references in the vidivi images configuration file from mosipdev to mosipdev2 and standardized version tag format from duplicate tags (e.g., "release-1.3.x release-1.3.x") to a two-part format (e.g., "release-1.3.x 1.3.x").

Changes

Cohort / File(s) Summary
Image registry and tag updates
release/vidivi/images.txt
Updated all image repository references from mosipdev to mosipdev2; standardized version tag format across all entries from duplicate release tags to release and version tag pairs

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

  • Single configuration file with repetitive, homogeneous updates across entries
  • Changes are mechanical substitutions of registry names and tag format normalization
  • No logic impact or functional complexity

Possibly related PRs

Suggested reviewers

  • ckm007

Poem

🐰 From dev to dev2, the images hop,
Tags aligned in a neat, tidy crop,
Registry refs take a modernish leap,
Configuration dreams, so wholesome and deep! 📦

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Title check ⚠️ Warning The PR title mentions 'mosipdev2 to mosipqa', but the actual changes update image references from 'mosipdev to mosipdev2' with version tag reformatting. Update the title to accurately reflect the actual changes, such as 'DSD-9452 Update mosipdev to mosipdev2 image references' or similar to match the content of the changeset.
✅ 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

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ae75469 and ac321bf.

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

1-15: PR title is misleading. The changes update from mosipdev to mosipdev2, not to mosipqa as the title suggests.

The git history confirms that all 15 images were successfully transferred to mosipdev2. The PR title "DSD-9452 mosipdev2 to mosipqa" incorrectly implies the target registry is mosipqa, but the actual changes stop at mosipdev2. Either rename the PR title to reflect the actual change ("mosipdev to mosipdev2") or complete the remaining migration to mosipqa if that was the intended scope.

Likely an incorrect or invalid review 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.

@abhishek8shankar
abhishek8shankar merged commit d226c6e into mosip:release-1.2.0.1 Dec 10, 2025
1 of 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