Prepare v1.1.0 release#235
Conversation
- Bump VERSION_NAME from 1.1.0-SNAPSHOT to 1.1.0 - Add CHANGELOG entry for v1.1.0 (JDK 17 downgrade, Plugin Portal publishing) - Update comparison links in CHANGELOG footer
Review Summary by QodoPrepare v1.1.0 release WalkthroughsDescription• Bump VERSION_NAME from 1.1.0-SNAPSHOT to 1.1.0 • Add CHANGELOG entry for v1.1.0 release with two key changes - JDK 17 downgrade for wider consumer compatibility - Gradle Plugin Portal publishing via dedicated workflow • Update CHANGELOG comparison links for v1.1.0 release Diagramflowchart LR
A["Version 1.1.0-SNAPSHOT"] -->|Bump Version| B["Version 1.1.0"]
B -->|Update CHANGELOG| C["Add Release Entry"]
C -->|Document Changes| D["JDK 17 Downgrade & Plugin Portal"]
B -->|Update Links| E["Comparison Links"]
File Changes1. gradle.properties
|
There was a problem hiding this comment.
Pull request overview
Prepares the repository for the v1.1.0 release by moving the build version from a snapshot to a release version and recording the release notes in the changelog.
Changes:
- Bump
VERSION_NAMEfrom1.1.0-SNAPSHOTto1.1.0for the release. - Add a
1.1.0changelog section dated2026-06-03and update comparison links.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
gradle.properties |
Updates VERSION_NAME to the 1.1.0 release value. |
CHANGELOG.md |
Adds the 1.1.0 release notes and updates footer compare links. |
| ### Changed | ||
|
|
||
| - Lowered the minimum supported JDK / JVM bytecode target from 21 to 17. Featured artifacts now target JVM 17, widening consumer compatibility — projects on JDK 17 toolchains can now consume the library. Consumers on newer JDKs are unaffected. (#233) | ||
| - The Gradle plugin and its plugin marker artifact are now published to the Gradle Plugin Portal via a dedicated workflow; the Maven Central listing is kept free of plugin-marker artifacts. (#228, #231) |
There was a problem hiding this comment.
1 issue found across 2 files
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="CHANGELOG.md">
<violation number="1" location="CHANGELOG.md:13">
P3: "its plugin marker artifact" should be plural — Gradle publishes one marker artifact per plugin ID registered in `gradlePlugin {}`. Use "its plugin marker artifacts" for accuracy (the second half of this sentence already uses the plural correctly).</violation>
</file>
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
| ### Changed | ||
|
|
||
| - Lowered the minimum supported JDK / JVM bytecode target from 21 to 17. Featured artifacts now target JVM 17, widening consumer compatibility — projects on JDK 17 toolchains can now consume the library. Consumers on newer JDKs are unaffected. (#233) | ||
| - The Gradle plugin and its plugin marker artifact are now published to the Gradle Plugin Portal via a dedicated workflow; the Maven Central listing is kept free of plugin-marker artifacts. (#228, #231) |
There was a problem hiding this comment.
P3: "its plugin marker artifact" should be plural — Gradle publishes one marker artifact per plugin ID registered in gradlePlugin {}. Use "its plugin marker artifacts" for accuracy (the second half of this sentence already uses the plural correctly).
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At CHANGELOG.md, line 13:
<comment>"its plugin marker artifact" should be plural — Gradle publishes one marker artifact per plugin ID registered in `gradlePlugin {}`. Use "its plugin marker artifacts" for accuracy (the second half of this sentence already uses the plural correctly).</comment>
<file context>
@@ -5,6 +5,13 @@ All notable changes to this project will be documented in this file.
+### Changed
+
+- Lowered the minimum supported JDK / JVM bytecode target from 21 to 17. Featured artifacts now target JVM 17, widening consumer compatibility — projects on JDK 17 toolchains can now consume the library. Consumers on newer JDKs are unaffected. (#233)
+- The Gradle plugin and its plugin marker artifact are now published to the Gradle Plugin Portal via a dedicated workflow; the Maven Central listing is kept free of plugin-marker artifacts. (#228, #231)
+
## [1.0.0] - 2026-05-30
</file context>
| - The Gradle plugin and its plugin marker artifact are now published to the Gradle Plugin Portal via a dedicated workflow; the Maven Central listing is kept free of plugin-marker artifacts. (#228, #231) | |
| - The Gradle plugin and its plugin marker artifacts are now published to the Gradle Plugin Portal via a dedicated workflow; the Maven Central listing is kept free of plugin-marker artifacts. (#228, #231) |
Summary
gradle.properties: bumpVERSION_NAMEfrom1.1.0-SNAPSHOTto1.1.0CHANGELOG.md: add[1.1.0] - 2026-06-03section with two entries (JDK 17 downgrade Lower JVM target from 21 to 17 #233, Plugin Portal publishing Publish Gradle plugin to Plugin Portal, keep Central listing clean #228 Extract Gradle Plugin Portal publish into a separate dispatchable workflow #231); update footer comparison links ([Unreleased]now points tov1.1.0...HEAD, new[1.1.0]link added)README.md: no changes — all version references use<version>placeholders and there are no JDK/Java version requirements statedREADME check
Searched for hardcoded library versions (
1.0.0) and JDK/Java 21 requirements — none found. README untouched.Not included
Do not merge — CI must pass first.