Align versions and update README for release-1.x#41
Conversation
Updates the project and parent POMs to microsphere-spring-cloud 0.1.24 for version alignment. Also marks `microsphere-java-core` as an optional dependency in `microsphere-hibernate-core` so it is not forced transitively onto downstream consumers.
Refresh the branch matrix in README.md to reflect the latest released versions: main from 0.2.7 to 0.2.8 and 1.x from 0.1.7 to 0.1.8.
Codecov Report✅ All modified and coverable lines are covered by tests. 🚀 New features to boost your workflow:
|
🤖 Augment PR SummarySummary: Aligns this repo with Microsphere Spring Cloud 🤖 Was this summary useful? React with 👍 or 👎 |
| <dependency> | ||
| <groupId>io.github.microsphere-projects</groupId> | ||
| <artifactId>microsphere-java-core</artifactId> | ||
| <optional>true</optional> |
There was a problem hiding this comment.
Marking microsphere-java-core as optional means downstream users of microsphere-hibernate-core won’t get it transitively, but several public classes appear to depend on it (e.g., DelegatingInterceptor implements io.microsphere.lang.DelegatingWrapper). That can lead to NoClassDefFoundError/compile issues for consumers unless they manually add microsphere-java-core.
Severity: high
🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.
63cf81c
into
microsphere-projects:release-1.x
This pull request updates dependency versions and documentation to ensure compatibility with the latest releases. The most important changes are grouped below:
Dependency version updates:
pom.xmlto0.1.24to align with the latestmicrosphere-spring-cloud-parentrelease.microsphere-spring-cloud.versionproperty inmicrosphere-hibernate-parent/pom.xmlfrom0.1.23to0.1.24.microsphere-java-coredependency as optional inmicrosphere-hibernate-core/pom.xmlto clarify its usage.Documentation updates:
README.mdto reflect the new released versions:mainbranch to0.2.8and1.xbranch to0.1.8.