Repository navigation
Conversation
The first Maven Central release is where MADR 0003 said to revisit the version scheme. A library API is what SemVer describes, and JabRef's html-to-node already publishes this way, so chatpane adopts its setup: - :chatpane applies com.vanniktech.maven.publish as org.jabref:chatpane: signed jar, sources, javadoc of the exported packages only, Apache-2.0 POM. The version lives in gradle.properties (chatpaneVersion). - publish.yml publishes snapshots of main and <version>-PR<n>-SNAPSHOT for same-repo pull requests; release.yml releases on a v* tag and refuses a tag that disagrees with chatpaneVersion. - CHANGELOG.md moves to an Unreleased section (heylogs versioning=semver); no daily date tag had been pushed, so nothing is lost. - AGENTS.md drops the daily tagging ritual and describes the release steps. Javadoc gets every source file from Gradle, so the internal package is excluded explicitly and its classes patched into the module, as html-to-node does. Blocked on maintainers: the signing and Central secrets (same names as html-to-node) must be added to the repository. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Taken over from html-to-node: daily Gradle and weekly GitHub Actions updates; automerge.yml approves and squash-merges bot PRs and same-repo PRs titled like dependency bumps or labelled automerge. Needs "Allow auto-merge" enabled in the repository settings. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Member
|
Supersed by #2 |
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
2 participants
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
Prepares ChatPane for Maven Central as
org.jabref:chatpane, with the same publishing setup as html-to-node: signed snapshots ofmainand of each pull request, and a release for every pushedv<version>tag.The first release makes the version scheme a real decision, so MADR 0012 switches from daily CalVer to SemVer (starting at
0.1.0-SNAPSHOT) and supersedes MADR 0003's versioning.Dependabot and the auto-merge workflow for its PRs come along as well.
Before this can publish, a maintainer has to:
KOPPOR_SIGNING_KEYID,KOPPOR_SIGNING_PASSWORD,KOPPOR_SIGNING_SECRETKEYRINGFILE_BASE64,KOPPOR_MAVENCENTRALUSERNAMEandKOPPOR_MAVENCENTRALPASSWORD(the same names html-to-node uses);automerge.ymlneeds.Steps to test
gradlew :chatpane:publishToMavenLocal -x signMavenPublication~/.m2/repository/org/jabref/chatpane/0.1.0-SNAPSHOT/: it holds the jar, sources, javadoc (only theorg.jabref.chatpaneandorg.jabref.chatpane.skinpackages), a POM with Apache-2.0 and the JavaFX dependency without classifier, and Gradle module metadata.gradlew -q :chatpane:properties -PversionSuffix=PR7showsversion: 0.1.0-PR7-SNAPSHOT.Publish snapshot to Maven Centralrun publishes0.1.0-PR<n>-SNAPSHOT.Related issues and pull requests
None.
AI usage
Claude Code (model claude-opus-5-5) adapted html-to-node's workflows and wrote the Gradle publishing setup, MADR 0012 and the documentation changes.
AI Influence Level: high. The author chose the approach (SemVer, which workflows to take over) and reviewed every change.
Checklist
CHANGELOG.mdentry for user-visible changesREADME.md/docs/updated🤖 Generated with Claude Code