Fix parent POM version in new module

[GunalKupta]

What

Parent POM version inconsistency caused by pint merging a new module.

Checklist

• Contains customer facing changes? Including API/behavior changes
• Is this change gated behind feature flag(s)?
  • List the LD flags needed to be set to enable this change
• Did you add sufficient unit test and/or integration test coverage for this PR?
  • If not, please explain why it is not required
  • No code change
• Does this change require modifying existing system tests or adding new system tests?
  • If so, include tracking information for the system test changes

References

JIRA:

Test & Review

Open questions / Follow-ups

[confluent-cla-assistant]

🎉 All Contributor License Agreements have been signed. Ready to merge.
_{Please push an empty commit if you would like to re-run the checks to verify CLA status for all contributors.}

[sonarqube-confluent]

• 0.00% Coverage on New Code (is less than 80.00%)

Analysis Details

2744 Issues

• 70 Bugs
• 15 Vulnerabilities
• 2659 Code Smells

Coverage and Duplications

• 0.00% Coverage (0.00% Estimated after merge)
• No duplication information (2.40% Estimated after merge)

Project ID: schema-registry

View in SonarQube