Updated pom version

[pvsaidurga]

Summary by CodeRabbit

• Chores
  • Synchronized project versions to 1.4.0-SNAPSHOT across multiple plugins
  • Upgraded esignet core dependency to 1.8.0-SNAPSHOT
  • Upgraded esignet-signup dependency to 1.4.0-SNAPSHOT

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

[coderabbitai]

Walkthrough

Three Maven plugin modules are updated with synchronized version bumps: project version to 1.4.0-SNAPSHOT, esignet.version to 1.8.0-SNAPSHOT, and esignet-signup.version to 1.4.0-SNAPSHOT.

Changes

Cohort / File(s)	Change Summary
Version and Dependency Updates mock-plugin/pom.xml, mosip-identity-plugin/pom.xml, sunbird-rc-plugin/pom.xml	Project version bumped to 1.4.0-SNAPSHOT; esignet.version updated to 1.8.0-SNAPSHOT; esignet-signup.version updated to 1.4.0-SNAPSHOT

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Simple, homogeneous version updates applied consistently across three files
• No logic changes, build behavior modifications, or functional impact
• Straightforward dependency version synchronization

Possibly related PRs

• [ES-2394] java21 migration Mosip identity plugin #177 — Modifies Maven properties in mosip-identity-plugin/pom.xml (esignet.version and build properties)
• [DSD-9388] eSignet 1.7.0 release changes #179 — Updates same Maven POM properties (project version, esignet.version, esignet-signup.version) across plugin modules
• [ES-2393] Mock plugin java11 to java21 migration #176 — Updates Maven POM properties in mock-plugin/pom.xml (esignet.version and esignet-signup.version)

Suggested reviewers

• sacrana0
• ase-101

Poem

🐰 Versions hop along the line,
From 1.3.5 to 1.4 so fine,
Dependencies aligned with care,
Esignet's update floating everywhere!
Three plugins dance in harmony,
Release notes complete and free! 📦✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Updated pom version' is vague and generic, failing to specify which versions were updated or across which modules.	Consider using a more descriptive title such as 'Bump plugin versions to 1.4.0 and esignet dependencies' to clearly communicate the scope and nature of the version updates.

✅ 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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

mosip-identity-plugin/pom.xml (1)

6-8: Restore standard POM element ordering.

The <version> element should follow <artifactId>, not precede it. The conventional POM element order is groupId, artifactId, version. While Maven will parse this correctly, restoring standard ordering improves consistency.

Apply this diff to restore standard POM element ordering:

-	<groupId>io.mosip.esignet</groupId>
-    <version>1.4.0-SNAPSHOT</version>
-	<artifactId>mosip-identity-plugin</artifactId>
+	<groupId>io.mosip.esignet</groupId>
+	<artifactId>mosip-identity-plugin</artifactId>
+	<version>1.4.0-SNAPSHOT</version>

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e52adcb and 2aa5278.

📒 Files selected for processing (3)

• mock-plugin/pom.xml (2 hunks)
• mosip-identity-plugin/pom.xml (2 hunks)
• sunbird-rc-plugin/pom.xml (2 hunks)

🔇 Additional comments (3)

sunbird-rc-plugin/pom.xml (1)

7-7: Version bump is consistent with other modules in the PR.

The project version and esignet.version updates align across all three plugin modules. No POM structure or dependency ordering issues identified.

Also applies to: 83-83

mock-plugin/pom.xml (1)

8-8: Version bumps are synchronized and correctly used by dependencies.

The esignet-signup.version property is newly added and properly referenced by signup-integration-api dependency at line 145. All version changes maintain consistency with the overall PR objective.

Also applies to: 89-90

mosip-identity-plugin/pom.xml (1)

89-90: Version bumps are synchronized across all modules.

The esignet and esignet-signup version properties are updated consistently with the other plugin modules. Dependencies correctly reference these properties (esignet-core, esignet-integration-api, and signup-integration-api).