You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working on a locally hosted instance of Read The Docs with projects hosted in GitLab. For a couple of projects, the stable builds are stuck on an old branch (whereas typically stable stays up-to-date with the highest sequence tag).
Originally, this seemed like a project specific glitch, but it appears stable is pinned to the 16R branch for all the projects which contain that specific branch name.
Below are the attempts made so far to try and get the projects updating as expected, with no luck:
Restarting the server
Updating the stable Identifier in the Django project dashboard
Deleting and re-creating the project from the Django admin dashboard
Removing the 16R tag from the repo
Expected Result
I would expect that the stable build would remain in sync with the highest sequence git tag (similar to the behavior of other projects -- as shown below).
Actual Result
The stable build version is stuck on the 16R branch (shown below).
The text was updated successfully, but these errors were encountered:
@aklawren in case you are interested, the fix for this bug was already deployed, can you test if that really solves your problem? (you may need to wipe and rebuild another version).
You may need to do some additional steps if that doesn't work #3913 (comment)
Details
I'm working on a locally hosted instance of Read The Docs with projects hosted in GitLab. For a couple of projects, the
stable
builds are stuck on an old branch (whereas typicallystable
stays up-to-date with the highest sequence tag).Originally, this seemed like a project specific glitch, but it appears
stable
is pinned to the16R
branch for all the projects which contain that specific branch name.Below are the attempts made so far to try and get the projects updating as expected, with no luck:
Expected Result
I would expect that the stable build would remain in sync with the highest sequence git tag (similar to the behavior of other projects -- as shown below).

Actual Result
The stable build version is stuck on the

16R
branch (shown below).The text was updated successfully, but these errors were encountered: