Skip to content

Remove API docs for old versions and setup redirects #4457

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

Draft
wants to merge 5 commits into
base: gh-pages
Choose a base branch
from

Conversation

kleisauke
Copy link
Member

@kleisauke kleisauke commented Apr 7, 2025

See the individual commits for more details. Marked as draft as this PR assumes API/current points to API/8.17, so it can only be merged after the 8.17 release.

Rendered output: https://kleisauke.github.io/libvips/.

Test redirection URLs:
https://kleisauke.github.io/libvips/API/8.5
https://kleisauke.github.io/libvips/API/8.5/cpp (is just a symlink to /API/current/cpp)
https://kleisauke.github.io/libvips/API/8.5/VipsImage.html
https://kleisauke.github.io/libvips/API/8.5/using-from-python.html (the old GOI binding that now redirects to /API/current/examples.html)
https://kleisauke.github.io/libvips/API/current/Developer-checklist.html (uppercase to lowercase redirect)
... etc.

@jcupitt
Copy link
Member

jcupitt commented Apr 25, 2025

"The diff you're trying to view is too large. We only load the first 3000 changed files."

haha!

@jcupitt
Copy link
Member

jcupitt commented May 7, 2025

Shall we merge? It would be good to have some test 8.17 docs to look at.

@jcupitt
Copy link
Member

jcupitt commented May 7, 2025

... I copied the rendered html docs for 8.17 into API/8.17 for testing.

@jcupitt
Copy link
Member

jcupitt commented May 7, 2025

ahem and reverted, let's merge this first.

@kleisauke
Copy link
Member Author

Whoops, I rebased on top of f1c3927.

@kleisauke kleisauke force-pushed the gh-pages-8.17 branch 3 times, most recently from f27ca16 to 5d09d14 Compare May 7, 2025 18:59
@jcupitt
Copy link
Member

jcupitt commented May 8, 2025

Could you point current at 8.16? Then we can merge this before we release 8.17 and test it out a bit.

@kleisauke kleisauke mentioned this pull request May 8, 2025
@kleisauke
Copy link
Member Author

I just split the API docs for 8.17 to PR #4502. This PR can't be merged yet as the various redirects assumes API/current points to API/8.17.

@kleisauke kleisauke changed the title Add API docs for 8.17 and setup redirects Remove API docs for old versions and setup redirects May 8, 2025
kleisauke added 5 commits May 8, 2025 13:13
Except for 8.16, the latest one built with GTK-Doc.
That is:
```
$ cd API/
$ for link in 8.{5,6,7,8,9,10,11,12,13,14,15}; do ln -s _redirects $link; done
$ git add .
```
@jcupitt
Copy link
Member

jcupitt commented May 8, 2025

Ah I hadn't realised. Yes, that sounds reasonable.

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