Repository navigation
Conversation
The wrapper moves to Gradle 9.8.0, regenerated with `make upgrade-wrapper`, and CLAUDE.md names the new version. The author's convention plugins (gradle-plugins) go to 1.1.6 and Kover to 0.9.11. On the docs side, website/uv.lock picks up zensical 0.0.67 and markupsafe 3.0.4. None of these reach the published artifacts: they're build tooling only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Dokka 2.2.0 deprecates the top-level `dokka { suppressInheritedMembers }`
in favour of `DokkaPublication.suppressInheritedMembers`, and every build
that recompiles the script warns about it. The setting now sits inside
`dokkaPublications.html {}`, the only publication. The generated KDocs
are unchanged: JevRateLimitException's page still lists only retryAfter
and retryAfterMillis, linking to JevApiException for the rest.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
0.2.0 is tagged at 57a1dca with a v0.2.0 GitHub release, and jev4k and jev4k-jvm 0.2.0 are on Maven Central, signed, so the checklist's state table records that, with a row for the new group's coordinates. master shouldn't sit on a published version, so gradle.properties moves to 0.2.1 and the changelog gains an Unreleased section. The composite-build snippet tracks gradle.properties by design, so it moves too; the snippets that quote Central coordinates stay at 0.2.0, which is what consumers depend on. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Everything since the 0.2.0 tag is build and CI tooling: Gradle 9.8.0, Kover 0.9.11, the convention plugins at 1.1.6, newer setup-gradle and setup-uv actions, a newer Zensical for the site, and the Dokka deprecation fix. The library's API, behavior and dependencies are as in 0.2.0, so both documents say upgrading needs only the new version. The sections are headed "unreleased", as 0.1.0's were until it was dated, and the Unreleased section and its link give way to 0.2.1's. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Dependabot reports three denial-of-service advisories against the brace-expansion 2.1.4 that yarnResolutions pinned, in both the js and wasmJs lockfiles; 2.1.7 fixes all three. The lockfiles were regenerated as the build script's comment describes, and only that entry changed in each. It comes in through the Node.js test tooling and isn't part of any published artifact. make js-tests passes on both targets. The 0.2.1 changelog and release notes record it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The changelog and release notes replace "unreleased" with the date, as step 3 of the release checklist describes, and the checklist's state table records it. Their links already compare 0.2.0...0.2.1. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Step 3 of the release checklist: the README's Gradle, Maven and exclude-CIO lines, and the dependency-gradle, dependency-kmp, dependency-maven and exclude-cio snippets the Installation page shows, name the release. The "From 0.2.0 the group is com.pambrose.jev4k" notes stay, since they say when the coordinates moved. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
1 participant
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
0.2.1 is a maintenance release. The library's API, behavior and dependencies are unchanged from 0.2.0; everything here is build, CI and docs tooling, so upgrading needs only the new version number.
suppressInheritedMembersmoves intodokkaPublications.html {}, where Dokka 2.2.0 expects it. The generated KDocs are unchanged.brace-expansion2.1.7 (from 2.1.4), which closes the six open Dependabot alerts onmaster. It comes in through the Node.js test tooling and isn't in any published artifact.gradle.propertiesis at 0.2.1.CHANGELOG.mdandRELEASE_NOTES.mdhave 0.2.1 sections dated 2026-10-04. The release checklist's state table records the 0.2.0 release. The README and Installation-page install snippets name 0.2.1.Important
Don't merge until 0.2.1 is on Maven Central (release checklist, step 4). Merging puts the 0.2.1 install lines in the README on GitHub, so publish from this branch first (step 5), confirm both
curl -sIchecks return200, then squash-merge, tag0.2.1and create thev0.2.1release (step 6).Test plan
make jvm-tests: all pass, includingLiveSmokeTestagainst the real API.make js-tests: js 215 and wasmJs 214, no failures../gradlew dokkaGenerate: no deprecation warning, and inherited members are still hidden.uv run zensical build --clean --strict: "No issues found". The Installation page shows 0.2.1 in every install snippet.make testson a Mac (release checklist, step 2).make docker-linux-testsmake coverage-verifymake site-buildci-ok,docsand GitGuardian.🤖 Generated with Claude Code