apache / apache/pulsar

[Bug] pulsar-admin 2.x links don't properly link to 3.2

Open
#22,828 6 comments 0 reactions 0 assignees View on GitHub
type/bug
Dominant language
Java
Stars
15.3k
Forks
3.8k
Avg merge
1d 14h
Merged PRs (30d)
160

Description

### Search before asking

- [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.

### Read release policy

- [X] I understand that unsupported versions don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker.

### Version

Chrome

### Minimal reproduce step

Visit https://pulsar.apache.org/docs/2.10.x/pulsar-admin/ and click the `We recommend you use the 3.2.x.` link

### What did you expect to see?

The 3.2 docs

### What did you see instead?

![Screenshot 2024-06-03 at 11 12 59 AM](https://github.com/apache/pulsar/assets/618650/c2bf5a5a-dcf0-432b-8b4d-091773fc6966)

### Anything else?

_No response_

### Are you willing to submit a PR?

- [ ] I'm willing to submit a PR!

Contributor guide

Open the contributing guide

Research direction

Start at https://pulsar.apache.org/docs/2.10.x/pulsar-admin/ and inspect the `We recommend you use the 3.2.x.` link. Verify its destination against the published 3.2 documentation URL, then confirm that clicking it opens the 3.2 docs rather than an incorrect or unavailable page.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Bug
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.