chore: add changelog path filtering for Java client releases#170
chore: add changelog path filtering for Java client releases#170
Conversation
Add paths filter to jreleaser.yml so the Java client release changelog only includes commits affecting the Java client directory. Pin jreleaser-version to early-access since the paths feature (jreleaser/ jreleaser#2073) is not yet in a stable release. Closes #154
🛡️ Jit Security Scan Results✅ No security findings were detected in this PR
Security scan by Jit
|
There was a problem hiding this comment.
Pull request overview
Updates the Java client release configuration so generated GitHub release changelogs are scoped to commits that touch the Java client directory, and updates the release workflow to use a JReleaser build that includes native path filtering support.
Changes:
- Add
release.github.changelog.pathsfiltering to the Java client’sjreleaser.yml. - Set the Java client release workflow to use the
early-accessJReleaser version channel.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| agent-memory-client/agent-memory-client-java/jreleaser.yml | Filters changelog generation to only include commits affecting the Java client directory. |
| .github/workflows/release-java-client.yml | Switches JReleaser version selection to early-access to enable the new changelog path filtering feature. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| jreleaser-arguments: 'assemble --git-root-search' | ||
| clone-to-dist-repo: false | ||
| update-antora-version: false | ||
| jreleaser-version: 'early-access' |
There was a problem hiding this comment.
jreleaser-version: 'early-access' is a moving target rather than an actual pin, which can make releases non-reproducible (and can break unexpectedly if the early-access artifacts change). Prefer pinning to a specific early-access build/version (and optionally add a note/TODO to switch back to a stable version once the feature is released).
| jreleaser-version: 'early-access' | |
| # TODO: Switch to a stable JReleaser version once the needed features are released. | |
| jreleaser-version: '1.14.0-early-access-1' |
Summary
changelog.pathsfilter tojreleaser.ymlso Java client release changelogs only include commits affectingagent-memory-client/agent-memory-client-java/, instead of all commits in the monorepojreleaser-versiontoearly-accessin the release workflow since thepathsfeature (jreleaser/jreleaser#2073, merged Feb 21) is not yet in a stable JReleaser release (latest stable is v1.22.0)Test plan
jreleaser-versionback tolatestCloses #154
Note
Low Risk
Low risk: release automation/config-only changes; main impact is potentially altering the generated GitHub release notes and relying on an early-access JReleaser build.
Overview
Java client releases now generate changelogs filtered to commits that touch
agent-memory-client/agent-memory-client-java/viarelease.github.changelog.pathsinjreleaser.yml, avoiding monorepo-wide noise.The
release-java-clientworkflow pinsjreleaser-versiontoearly-accessso the release job can use this changelog path-filtering capability.Written by Cursor Bugbot for commit dda303d. This will update automatically on new commits. Configure here.