You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "adityamparikh (via GitHub)" <gi...@apache.org> on 2026/09/18 16:16:05 UTC
[PR] build(release): wire org.jetbrains.changelog and populate CHANGELOG.md [solr-mcp]
adityamparikh opened a new pull request, #221:
URL: https://github.com/apache/solr-mcp/pull/221
## Summary
Adds the [`org.jetbrains.changelog`](https://github.com/JetBrains/gradle-changelog-plugin) Gradle plugin (2.5.0) and a Keep a Changelog-format `CHANGELOG.md`, so the project has a release-notes source that isn't hand-assembled from git log at release time.
- `[Unreleased]` section reflects recent user-facing changes: JSON documents-array indexing, CSV/XML forwarding straight to Solr's update handlers, `solr.url` fail-fast validation, and the native-image STDIO logging fix.
- Entries are added by hand to `[Unreleased]` as PRs land. At release time, `patchChangelog` promotes `[Unreleased]` into a versioned section, and `getChangelog --project-version=<version-or-Unreleased>` extracts one version's notes for reuse (e.g. as a GitHub Release body or an announcement email).
## Why manual entries, not commit-driven automation
This deliberately matches the direction already settled on in this repo: PR #34 (release-please) and PR #35 (git-semver-plugin) both proposed fully commit-driven changelog/semver generation and were closed in favor of hand-written entries. `org.jetbrains.changelog` only extracts/patches a manually-maintained section — it does not generate entries from commit messages.
## Note on the `dev-docs/release-process.md` reference
The build script comment points to the release-process doc as "apache/solr-mcp#157 (will land as dev-docs/release-process.md)" rather than a file path, since that PR is still open and the file doesn't exist on `main` yet. Once #157 merges this can be simplified to a direct path in a follow-up.
## Testing
- `./gradlew build` — BUILD SUCCESSFUL, all tests/RAT/spotless green.
- `./gradlew getChangelog --project-version=Unreleased` — verified output matches `CHANGELOG.md`'s `[Unreleased]` section.
- `./gradlew help --task patchChangelog` — verified the task registers correctly (not run for real, since that would cut a version section prematurely).
🤖 Generated with [Claude Code](https://claude.com/claude-code)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org
Re: [PR] build(release): wire org.jetbrains.changelog and populate CHANGELOG.md [solr-mcp]
Posted by "adityamparikh (via GitHub)" <gi...@apache.org>.
adityamparikh commented on PR #221:
URL: https://github.com/apache/solr-mcp/pull/221#issuecomment-5732844283
@epugh — this one is standalone build-only, doesn't touch the release-process branch or fork. Ready for a look whenever.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org
Re: [PR] build(release): wire org.jetbrains.changelog and populate CHANGELOG.md [solr-mcp]
Posted by "epugh (via GitHub)" <gi...@apache.org>.
epugh merged PR #221:
URL: https://github.com/apache/solr-mcp/pull/221
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org