Update metaschema-java to 3.0.0.M3 and liboscal-java to 7.1.0

[david-waltermire]

Summary

• Update metaschema-java from 3.0.0-SNAPSHOT to 3.0.0.M3
• Update liboscal-java from 7.1.0-SNAPSHOT to 7.1.0

Full CI build (mvn install -PCI -Prelease) passes with all 309 tests succeeding and no checkstyle, PMD, SpotBugs, or coverage issues.

Summary by CodeRabbit

• Chores
  • Updated metaschema-framework dependency to version 3.0.0.M3
  • Updated liboscal-java dependency to version 7.1.0

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request updates Maven dependency versions in pom.xml, transitioning metaschema-framework from version 3.0.0-SNAPSHOT to 3.0.0.M3 (milestone release) and liboscal-java from 7.1.0-SNAPSHOT to 7.1.0 (stable release).

Changes

Cohort / File(s)	Summary
Dependency Version Updates pom.xml	Updated metaschema-framework.version to 3.0.0.M3 and liboscal-java.version to 7.1.0, promoting snapshot dependencies to stable/milestone releases.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Update dependencies to latest releases #207: Updates the same pom.xml dependency properties (metaschema-framework.version and liboscal-java.version).
• Update metaschema-java to 3.0.0.M3 liboscal-java#253: Modifies the identical metaschema-framework version property from snapshot to milestone release.
• build: update dependencies for next development iteration #234: Transitions the same Maven properties in pom.xml to stable/milestone versions.

Poem

🐰 Hop, hop! The versions are bumped with care,
From snapshots to milestones, so shiny and fair!
Stable releases now greet the day,
Dependencies updated—let's celebrate the way! 🎉

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title directly and specifically describes the main change: updating two dependency versions in the project. It accurately summarizes the primary purpose of the pull request.
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.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

No actionable comments were generated in the recent review. 🎉

---

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