Skip to content

Prepare 2.6.0 for release - #20

Merged
perNyfelt merged 1 commit into
mainfrom
release/2.6.0
Nov 15, 2026
Merged

perNyfelt merged 1 commit into
mainfrom
release/2.6.0

Conversation

@perNyfelt

Copy link
Copy Markdown
Member

Set the project version to 2.6.0 and date its release notes 2026-11-15. Refresh the release documentation so maintainers can validate and publish the prepared artifacts consistently.

  • Document the renamed combined bundle's upgrade path and the JDK 17 build requirement.
  • Add maintainer release instructions, including Plugin Portal validation and recovery when Portal publication fails after Central publication.
  • Clarify that the build's 2.3.0 bootstrap plugin dependency is separate from the release version.
  • Fix README heading structure and document locale-independent Windows journal retries and UTF-8 decoding.

Validation on macOS ARM64 with JDK 17:

  • ./gradlew clean build -PrequireShellHarness=true passed: 200 tests passed, three Windows-only tests skipped; includes charset checks, plugin validation, and the publishing-script harness.
  • ./gradlew publishPlugins --validate-only passed.
  • Generated the Maven Central POM locally and checked release coordinates and required metadata. All generated publication POMs and main/sources/Javadoc JAR filenames use 2.6.0.
  • Checked all four plugin version snippets, local documentation links and anchors, and git diff --check.

No artifacts have been published.

@perNyfelt
perNyfelt merged commit 469e211 into main Nov 15, 2026
6 checks passed
@perNyfelt
perNyfelt deleted the release/2.6.0 branch November 15, 2026 20:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant