Skip to content

Conversation

@henrymercer
Copy link
Contributor

The backslash is necessary for RST formatting but leads to incorrect Markdown formatting.

@henrymercer henrymercer requested a review from a team as a code owner February 2, 2026 12:24
Copilot AI review requested due to automatic review settings February 2, 2026 12:24
Copy link
Contributor

@andersfugmann andersfugmann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates Kotlin version-range notation in Java QL library release notes/changelog to avoid an RST-escape backslash that renders incorrectly in Markdown.

Changes:

  • Remove the \ escape before *x* in several Kotlin version range entries.
  • Align formatting across individual release-note files and the consolidated CHANGELOG.md.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File Description
java/ql/lib/change-notes/released/7.5.0.md Fixes Markdown formatting for the Kotlin “2.2.2x” version range note.
java/ql/lib/change-notes/released/7.2.0.md Fixes Markdown formatting for the Kotlin “2.2.0x” version range note.
java/ql/lib/change-notes/released/4.1.0.md Fixes Markdown formatting for the Kotlin “2.1.0x” version range note.
java/ql/lib/CHANGELOG.md Fixes the same Markdown formatting issue for multiple Kotlin version range entries.

@henrymercer
Copy link
Contributor Author

Relevant CI checks have passed.

@henrymercer henrymercer merged commit 57c2208 into codeql-cli-2.24.1 Feb 2, 2026
10 of 15 checks passed
@henrymercer henrymercer deleted the henrymercer/kotlin/version-range-formatting branch February 2, 2026 12:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants