Prepare v0.6.1 release#194
Merged
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
Prepares the v0.6.1 patch release by aligning versions across Maven/Gradle artifacts and docs, adding the corresponding changelog entry, and adjusting the tag-triggered release workflow to draft the GitHub Release before publishing artifacts and only promote it after publishing succeeds.
Changes:
- Bump project version from
0.6.0to0.6.1across Maven POMs and the Gradle plugin build. - Update README distribution and usage examples to reference
0.6.1. - Add
0.6.1changelog entry and reorder the release workflow to create a draft GitHub Release earlier, then publish it last.
Reviewed changes
Copilot reviewed 9 out of 9 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| README.md | Updates CLI jar filename and published coordinates/examples to 0.6.1. |
| pom.xml | Bumps parent Maven version to 0.6.1. |
| core/pom.xml | Aligns module parent version to 0.6.1. |
| cli/pom.xml | Aligns module parent version to 0.6.1. |
| maven-plugin/pom.xml | Aligns module parent version to 0.6.1. |
| gradle-plugin/pom.xml | Aligns module parent version to 0.6.1. |
| gradle-plugin/build.gradle.kts | Bumps Gradle plugin project version to 0.6.1. |
| CHANGELOG.md | Adds the 0.6.1 release notes section. |
| .github/workflows/release.yml | Creates a GitHub Release as a draft before public publishing steps, then promotes it after publish succeeds. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
Summary
v0.6.1patch release across Maven, Gradle, and consumer-facing docs0.6.1changelog entry for the fixes and maintenance merged sincev0.6.0Review focus
.github/workflows/release.yml: draft creation happens before public publish steps, and final release promotion happens lastgradle-plugin/build.gradle.kts, README examples, and changelogValidation
C:\Program Files\Git\bin\bash.exe ./.github/scripts/verify-version-alignment.sh --expected-version 0.6.1git diff --checkgit grep -n -F "v0.6.0" -- .git grep -n -F "0.6.0" -- pom.xml core/pom.xml cli/pom.xml gradle-plugin/pom.xml maven-plugin/pom.xml gradle-plugin/build.gradle.kts README.md .github/workflows/release.ymlResidual risk
The actual registry publication still depends on the tag-triggered Release workflow and configured repository secrets.
Closes #193