adityamparikh opened a new pull request, #254: URL: https://github.com/apache/solr-mcp/pull/254
Writes the 1.0.0 release notes into `CHANGELOG.md` and fixes the release-time steps for the `org.jetbrains.changelog` plugin so that cutting 1.0.0 produces a correct section. ## Release notes `[Unreleased]` now holds what 1.0.0 will publish: - A **summary** paragraph (the plugin's term for text between the version heading and its first `###` group) giving the release's highlights. `patchChangelog` keeps it, and `getChangelog` prints it first, so it opens the vote email and the GitHub Release body. - One **Added** entry per user-facing capability: search, indexing in four formats, collection and alias management, schema tools, prompts/resources/completions, the two transports, OAuth2 on HTTP, the Docker images, observability, SBOM and license disclosure, and the client guides. The text describes the Spring Boot 4.1 / Spring AI 2.0 stack, so it is accurate once #23 is merged. The file changes themselves don't depend on #23. `Changed`, `Fixed` and `Security` are empty because they describe differences from a previous release. `patchChangelog` drops empty groups from the released section. ## Release-step fixes - **The documented version cut produced the wrong heading.** `./gradlew patchChangelog -Pversion=1.0.0` writes `## [1.0.0-SNAPSHOT]`, because `build.gradle.kts` assigns `version` itself and overrides the property. `release-process.md` step 1 now runs `./gradlew patchChangelog` right after its existing `sed` version bump, and adds `CHANGELOG.md` to the "prepare 1.0.0" commit, so the notes are in the voted source archive. - **Generated links pointed at tags that won't exist.** The plugin's default `versionPrefix` is `v`, giving `.../commits/v1.0.0`. `release-process.md` tags `releases/solr-mcp/1.0.0`, so the build now sets `versionPrefix = "releases/solr-mcp/"`. - `CHANGELOG_GUIDE.md` documents the summary for future releases, and its preview command no longer passes `--no-summary`, which hid the highlights. The first-release section now says the history has been back-filled rather than describing it as a pending task. ## Tag naming needs a decision `release-process.md` creates `releases/solr-mcp/1.0.0-rc1`, but `release-publish.yml` checks out `v1.0.0-rc1` and looks up a `v1.0.0` GitHub Release. Run against the documented tags, the publish workflow fails at its tag check. This PR follows `release-process.md`. If `v<version>` is the intended scheme, `versionPrefix` should change to match. ## Verification - `./gradlew build -x rat` passes (464 tests, 0 failures, 0 skipped). `rat` fails on `main` itself because `solr-mcp-ip-clearance.xml` has no license header; this PR doesn't touch that file. - Dry run on a copy with `version = "1.0.0"`: `patchChangelog` produced `## [1.0.0] - <date>` with the summary and `Added` only, and links `.../compare/releases/solr-mcp/1.0.0...HEAD` and `.../commits/releases/solr-mcp/1.0.0`. `getChangelog --no-header --project-version=1.0.0` printed the summary followed by the `Added` entries. - The bootJar contains `META-INF/sbom/application.cdx.json`, `META-INF/LICENSE` and `META-INF/NOTICE`, as the notes state. 🤖 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
