Repository navigation
Include GitHub issues in the release notes built by build-changelog.sh (9.x) - #1703
Merged
Merged
Conversation
This was referenced Oct 23, 2026
build-changelog.sh built the release notes only from Apache Jira: it looked up the version id on Jira's ReleaseNote.jspa page and copied that page's text notes into the changelog. Issues are filed on GitHub now, so their fixes never reached the changelog. The page also answers anonymous requests with 401 by now, so the script failed for every version, and Jira is read-only, so a Jira issue fixed since can no longer be resolved or given a fix version. The script now builds the notes of a release from the commits since the previous release: - Jira issues: the ones resolved as Fixed with the release as fix version, through the anonymous REST API, plus the ones whose key is in the subject of a commit in the range and of no commit before it. An issue resolved otherwise than as Fixed is left out. - GitHub issues: the ones referenced in a commit subject, or in the body as "GitHub issue #N" or after fixes, closes or resolves. A pull request contributes the issues it closes. Issues closed as not planned or as duplicates are left out. - A GitHub issue whose title starts with a Jira key, as in "[WICKET-1234] Summary", is a copy of that Jira issue and is listed under the Jira key only. The previous release is the rel/wicket-* tag with the highest version below the one being built; --since overrides it. GitHub issues get the [GH-N] key and are grouped by their issue type: Bug, Feature (as New Feature) and Task. The layout of the notes is unchanged, so release.sh still reads them. Before it touches the changelog, the script stops with an error when a GitHub issue in the notes is still open, a GitHub copy of a Jira issue in the notes is open, or a GitHub issue has no type. Closing an issue is left to a person, once every branch that needs the fix has it; --force merges the notes anyway. The script now runs under bash and needs jq and a logged-in GitHub CLI. A version given as argument is used as is, and a changelog that does not exist yet is created. Backport of 153eda1..ad352df from master. GitHub issue #1699 Generated-by: Claude Code (Claude Opus 5.5)
dashorst
force-pushed
the
changelog-github-issues-9.x
branch
from
October 23, 2026 12:11
4a5ba98 to
fe5553a
Compare
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
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.
Backport of #1701 to
wicket-9.x, part of #1699. The backport is one commit, squashed from the five on master (153eda1..ad352df); the script is identical to master's. 9.25.0 combines WICKET-7205, which has 9.25.0 as fix version, WICKET-7199, which is still open in Jira and comes from the commit subjects, and GitHub issues.Regenerating a release's notes needs the
rel/wicket-*tags fetched: the previous tag sets the commit range.Output on wicket-9.x (9.25.0)
Run at this branch's tip with
--forceand Enter at the prompt. Without--forcethe run ends after the list of open issues and leaves the changelog unchanged. GH-1699 is listed, and flagged as open, because this branch's own commit references it.🤖 Generated with Claude Code