Skip to content

Fix formatting of PR refs in release notes#23434

Open
mikeCRL wants to merge 6 commits into
mainfrom
fix-rn-issue-ref-indendation
Open

Fix formatting of PR refs in release notes#23434
mikeCRL wants to merge 6 commits into
mainfrom
fix-rn-issue-ref-indendation

Conversation

@mikeCRL
Copy link
Copy Markdown
Contributor

@mikeCRL mikeCRL commented Jun 1, 2026

Fixed instances of PR references being interpreted as H1 headings.

Since #23301, instances of continuation text (multi-paragraph bullets) followed by an PR reference on its own line, would have that reference and all others in the section (until the next intentional heading) interpreted as H1s.

This may have only affected sections of 3 releases' notes, but to be thorough/consistent, I made the following changes across the board:

  • For single-line bullets, moved the reference to the end of the bullet's single line.
  • For continuation bullets, matched the indentation of the continuation text, and prepended a \ to the reference.

Example changes:

For single-line bullets:

Before:

- Fixed a slow memory leak that was introduced in v25.1.8.
 #149921

After:

- Fixed a slow memory leak that was introduced in v25.1.8. #149921

For continuation bullets:

Before:

- The `RESET ALL` statement no longer affects the following session variables:
  - `is_superuser`
  - `role`
  - `transaction_read_only`
  
    This better matches PostgreSQL behavior for `RESET ALL`.
 #149388

After:

- The `RESET ALL` statement no longer affects the following session variables:
  - `is_superuser`
  - `role`
  - `transaction_read_only`
  
    This better matches PostgreSQL behavior for `RESET ALL`.

    \#149388

Example of the bug

From https://www.cockroachlabs.com/docs/releases/v25.2#v25-2-3:

Screenshot 2026-06-01 at 4 00 25 PM

Fix issue references that were being interpreted as markdown headings
by increasing their indentation to match preceding continuation text.

Co-Authored-By: roachdev-claude <roachdev-claude-bot@cockroachlabs.com>
@netlify
Copy link
Copy Markdown

netlify Bot commented Jun 1, 2026

Deploy Preview for cockroachdb-api-docs canceled.

Name Link
🔨 Latest commit abbed0c
🔍 Latest deploy log https://app.netlify.com/projects/cockroachdb-api-docs/deploys/6a1f115992dbe4000838dec3

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jun 1, 2026

Files changed:

@netlify
Copy link
Copy Markdown

netlify Bot commented Jun 1, 2026

Deploy Preview for cockroachdb-interactivetutorials-docs canceled.

Name Link
🔨 Latest commit abbed0c
🔍 Latest deploy log https://app.netlify.com/projects/cockroachdb-interactivetutorials-docs/deploys/6a1f11593d9b5b0008bce219

@netlify
Copy link
Copy Markdown

netlify Bot commented Jun 1, 2026

Deploy Preview for cockroachdb-docs canceled.

Name Link
🔨 Latest commit abbed0c
🔍 Latest deploy log https://app.netlify.com/projects/cockroachdb-docs/deploys/6a1f1159814ba60008fbd495

@mikeCRL mikeCRL changed the title fix: correct indentation of issue refs in release notes Fix indentation of some issue refs in release notes Jun 1, 2026
mikeCRL and others added 2 commits June 1, 2026 16:45
Add backslash escaping to issue references that would otherwise be
interpreted as markdown headings due to starting with #.

Co-Authored-By: roachdev-claude <roachdev-claude-bot@cockroachlabs.com>
Move all issue references to be inline at the end of simple
single-paragraph bullets instead of on their own lines, preventing
them from being interpreted as H1 headings.

This fixes 401 instances across 43 release note files.

Co-Authored-By: roachdev-claude <roachdev-claude-bot@cockroachlabs.com>
@mikeCRL mikeCRL changed the title Fix indentation of some issue refs in release notes Fix formatting of issue refs in release notes Jun 1, 2026
@mikeCRL mikeCRL requested review from ebembi-crdb and rmloveland June 1, 2026 21:19
@mikeCRL mikeCRL changed the title Fix formatting of issue refs in release notes Fix formatting of PR refs in release notes Jun 1, 2026
@ebembi-crdb
Copy link
Copy Markdown
Contributor

@mikeCRL is this a regression or is it something that was there from the beginning that started causing problems now?
Thanks for finding and fixing this

@mikeCRL
Copy link
Copy Markdown
Contributor Author

mikeCRL commented Jun 2, 2026

@ebembi-crdb I think what was already present pre-#23301 was that a handful of references were on their own line. It was against the normal style, but still interpreted the same as other references. Then, when #23301 came through, dropping the [ that preceded these (to unlink), # became the first non-space character on the line, so it started to be interpreted as an H1.

@rmloveland
Copy link
Copy Markdown
Contributor

@mikeCRL thanks for fixing this! LGTM

@mohini-crl mohini-crl enabled auto-merge June 2, 2026 16:55
@mohini-crl mohini-crl self-requested a review June 2, 2026 17:11
@mohini-crl mohini-crl disabled auto-merge June 2, 2026 17:15
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Copy link
Copy Markdown
Contributor

@ebembi-crdb ebembi-crdb left a comment

Choose a reason for hiding this comment

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

LGTM!

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants