Skip to content

Remove known limitations page#22325

Merged
taroface merged 15 commits into
mainfrom
remove-known-limitations-page
Jan 30, 2026
Merged

Remove known limitations page#22325
taroface merged 15 commits into
mainfrom
remove-known-limitations-page

Conversation

@taroface

Copy link
Copy Markdown
Contributor

Remove Known Limitations page on v26.1 and v25.4 as follows:

  • Move all inline content on known-limitations.md into dedicated includes.
    • Embed those includes on appropriate feature docs.
    • In one or two cases, the content didn't quite resemble a known limitation, so it was reincorporated as prescriptive guidance.
  • Update existing links to the Known Limitations page to point to those distributed includes.
    • Also redirect known-limitations.md to the Releases page. (Open to other suggestions.)
  • Delete known-limitations.md.
  • Remove Known Limitations from the sidebar. This probably removes it for all versions, but I feel it's OK?

@github-actions

github-actions Bot commented Jan 23, 2026

Copy link
Copy Markdown

Files changed:

@netlify

netlify Bot commented Jan 23, 2026

Copy link
Copy Markdown

Deploy Preview for cockroachdb-interactivetutorials-docs canceled.

Name Link
🔨 Latest commit cdbe802
🔍 Latest deploy log https://app.netlify.com/projects/cockroachdb-interactivetutorials-docs/deploys/697c3dc95820ae000730faa0

@netlify

netlify Bot commented Jan 23, 2026

Copy link
Copy Markdown

Deploy Preview for cockroachdb-api-docs canceled.

Name Link
🔨 Latest commit cdbe802
🔍 Latest deploy log https://app.netlify.com/projects/cockroachdb-api-docs/deploys/697c3dc9b0eef4000829560c

@github-actions

github-actions Bot commented Jan 23, 2026

Copy link
Copy Markdown

Cross-Version Link Check Passed

All cross-version link issues have been resolved. Good job!

@netlify

netlify Bot commented Jan 23, 2026

Copy link
Copy Markdown

Netlify Preview

Name Link
🔨 Latest commit cdbe802
🔍 Latest deploy log https://app.netlify.com/projects/cockroachdb-docs/deploys/697c3dc91bdcfa000800d44b
😎 Deploy Preview https://deploy-preview-22325--cockroachdb-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@mikeCRL mikeCRL self-requested a review January 27, 2026 15:41

@mikeCRL mikeCRL left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM! Some suggestions for your consideration.

Comment thread src/current/v25.4/set-vars.md Outdated
Comment thread src/current/v26.1/set-vars.md Outdated
<h4 id="v25-4-0-known-limitations">Known limitations</h4>

For information about new and unresolved limitations in CockroachDB v25.4, with suggested workarounds where applicable, refer to [Known Limitations]({% link v25.4/known-limitations.md %}).
{% include releases/v25.4/deprecations.md %} No newline at end of file

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I'm thinking we should have some note saying something like 'Known Limitations are now exclusively listed on applicable feature pages, and are no longer aggregated into a single page'.

If so, we could re-add the Known limitations heading after this, and just include that phrase there - just for v25.4 and v26.1.

WDYT?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I'm wondering if @Flat5flat9 could weigh in here. I feel it depends how much we think our customers refer to this section when upgrading.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@mikeCRL I discussed with @Flat5flat9 and we still want the Known Limitations section for each release to list the new limitations for that release -- this makes sense, and must have slipped my mind. So I've replaced this section with the new v25.4 new limitations, adding the usual commented-out placeholder block in case there are no new limitations (as might be the case in v26.1).

Comment thread src/current/_data/redirects.yml Outdated

# Removed Pages

- destination: releases/index.md

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

If you go with my suggestion on v25.4.0.md to re-add the Known Limitations section to the What's New page [with a simple note under it about the change], then I think it's better to redirect to that, like this:

  - destination: releases/v25.4.md#v25-4-0-known-limitations                                                 
    sources: ['known-limitations.md']                                                                        
    versions: ['v25.4']                                                                                      
                                                                                                             
  - destination: releases/v26.1.md#v26-1-0-known-limitations                                                 
    sources: ['known-limitations.md']                                                                        
    versions: ['v26.1']       

If not, then maybe it's better to just redirect to a search for Known Limitations: https://www.cockroachlabs.com/docs/search?query=%22Known+Limitations%22

@taroface taroface Jan 29, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Updated as follows (see above comment; I also removed the version from the anchor link, since it's the only Known Limitations heading on the page):

- destination: ../releases/25.4.md#known-limitations
  sources: ['known-limitations.md']
  versions: ['v25.4']

@taroface taroface force-pushed the remove-known-limitations-page branch from 6586bf6 to 7fd8826 Compare January 28, 2026 18:30
@taroface taroface force-pushed the remove-known-limitations-page branch 2 times, most recently from 875126b to 7d7094d Compare January 29, 2026 16:52
@taroface taroface force-pushed the remove-known-limitations-page branch from 5cf9ff7 to a570660 Compare January 30, 2026 03:55
@taroface taroface force-pushed the remove-known-limitations-page branch from ec73b63 to af503fa Compare January 30, 2026 04:50
@taroface taroface force-pushed the remove-known-limitations-page branch from af503fa to cdbe802 Compare January 30, 2026 05:12
@taroface taroface merged commit 7f0a7d6 into main Jan 30, 2026
6 checks passed
@taroface taroface deleted the remove-known-limitations-page branch January 30, 2026 05:24
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.

2 participants