Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cherrypick version switcher fixes to 2.36.0 #50448

Open
wants to merge 2 commits into
base: releases/2.36.0
Choose a base branch
from

Conversation

cristianjd
Copy link
Collaborator

Cherry picks the following PRs to version 2.36.0 to fix version switcher issues

#49892
#50292

Checks

  • I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
  • I've run scripts/format.sh to lint the changes in this PR.
  • I've included any doc changes needed for https://docs.ray.io/en/master/.
    • I've added any new APIs to the API Reference. For example, if I added a
      method in Tune, I've added it in doc/source/tune/api/ under the
      corresponding .rst file.
  • I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
  • Testing Strategy
    • Unit tests
    • Release tests
    • This PR is not tested :(

Looks like a sphynx update in verson 3.6.0 broke some of the layout this
resolves the issues
- adjusted the CSS to hide the default version picker that was covering
the Ask AI button
- moved the theme switched to navbar end so it shows up again
- add logic so the version detection of the pydata sphynx picker works
as expected for `release/2.4.0` for example

Before:
![Screenshot 2025-01-16 at 1 23
31 PM](https://github.com/user-attachments/assets/f877ba98-a753-41e9-b3b0-148575cd5904)

After:
![Screenshot 2025-01-16 at 1 23
09 PM](https://github.com/user-attachments/assets/4381904f-e1e7-4c09-bf5f-e393e99f62e3)

Signed-off-by: cristianjd <[email protected]>
## Why are these changes needed?
The version picker was not properly respecting the selected version.
This is due to the generated versions in the json being incorrect.

Fixed by updating the json generation logic to use versions of the form
`releases-2.42.0` instead `releases/2.24.0` and updated the version
match logic in `conf.py` back to just reading the version directly

Before:
![Screenshot 2025-02-06 at 12 31
55 PM](https://github.com/user-attachments/assets/7ca7669e-8a71-4612-b875-94955ed955fd)

After:
![Screenshot 2025-02-06 at 12 31
19 PM](https://github.com/user-attachments/assets/928581b8-2360-4b18-a87c-3b670212165e)



## Checks

- [x] I've signed off every commit(by using the -s flag, i.e., `git
commit -s`) in this PR.
- [x] I've run `scripts/format.sh` to lint the changes in this PR.
- [ ] I've included any doc changes needed for
https://docs.ray.io/en/master/.
- [ ] I've added any new APIs to the API Reference. For example, if I
added a
method in Tune, I've added it in `doc/source/tune/api/` under the
           corresponding `.rst` file.
- [ ] I've made sure the tests are passing. Note that there might be a
few flaky tests, see the recent failures at https://flakey-tests.ray.io/
- Testing Strategy
   - [ ] Unit tests
   - [ ] Release tests
   - [ ] This PR is not tested :(

---------

Signed-off-by: cristianjd <[email protected]>
@cristianjd cristianjd requested a review from a team as a code owner February 11, 2025 22:06
Copy link
Contributor

@angelinalg angelinalg left a comment

Choose a reason for hiding this comment

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

stamp

@pcmoritz pcmoritz added the go add ONLY when ready to merge, run all tests label Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
go add ONLY when ready to merge, run all tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants