Skip to content

Conversation

@VeckoTheGecko
Copy link
Contributor

OH. I just realised that this wouldn't surface in stable with the current configuration of the website (since stable points to the latest release). I'll see if I can update that in the RTD config, though nothing immediately jumps out...

Confirming that:

  • latest -> v4-dev
  • stable -> main

would be ideal?

Originally posted by @VeckoTheGecko in #1865 (comment)


I have updated the RTD configuration so that

  • latest points to main
  • stable points to the latest release
  • v4-dev points to v4-dev
  • latest is the default branch again when people go to the documentation

I think that this is much clearer than before and keeps existing documentation coherent (was trying to do this initially last week, but was running into some sync issues)

@VeckoTheGecko VeckoTheGecko changed the title doc: update link to v4 docs DOC: update link to v4 docs Feb 17, 2025
@VeckoTheGecko VeckoTheGecko merged commit 1381892 into main Feb 17, 2025
16 checks passed
@VeckoTheGecko VeckoTheGecko deleted the v/patch-link branch February 17, 2025 11:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants