Repository navigation
chore(release): prepare v1.5.2 - #155
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release v1.5.2
Patch release: dependency updates and build maintenance. No API changes.
Changes
1.5.21.5.3-SNAPSHOTFiles Modified
release-notes/RELEASE_NOTES_v1.5.2.md— new release notesREADME.md— dependency coordinates updatedbuild.gradle.kts— snapshot version bumpeddocs/.vitepress/versions.data.ts— docs version updatedWhat's in this release
Dependencies: Kotlin 2.4.20 → 2.4.21 · Spring Boot 4.1.1 → 4.1.2 · Spring Framework 7.0.9 → 7.0.10 · Spring Data JPA 4.1.1 → 4.1.2 · Spring Data Elasticsearch 6.1.1 → 6.1.2 · Jackson 3.2.2 → 3.2.3 · Hibernate ORM 7.4.7.Final → 7.4.13.Final · QueryDSL Feign 7.6 → 7.7
Build & Infrastructure: Gradle wrapper 9.7.1 → 9.8.2 · Spotless 8.10.2 → 8.10.4 · Gradle 10 deprecation fixes
Post-Merge Steps
After merging this PR, create and push the release tag to trigger CI publishing:
This will trigger the
publish.ymlworkflow which:Monitor: GitHub Actions