Version in ReadTheDocs retains the tags commit ID preventing a rebuild based on the updated commit for the TAG

[uhurusurfa]

Details

• Read the Docs project URL: [https://readthedocs.org/projects/{your_project_slug}/](https://readthedocs.org/projects/django-helpdesk/
• Build URL (if applicable): https://readthedocs.org/projects/{your_project_slug}/builds/{build_id}/

Expected Result

*When the tag associate with a version in ReadTheDocs is updated to a new commit and I go to ReadThgeDocs UI and force a rerun iof the failed build, it should fetch the latest code from the git repository using the tag rather than the commit number it retrieved first time round.

Actual Result

The build simply uses the same commit so there is no change to the outcome of the build.

Suggested feature or behaviour

Either fetch the code based on the tag or provide a way to delete the version in ReadTheDocs so that it can be properly rebuilt using the updarted commit.

[stsewd]

Hi, this is a known problem, currently you'll need to trigger two builds, the first build will update the commit tag, and the second build will actually build the tag with the new commit. I agree that we should just use the tag instead of the commit here.

[stsewd]

We had to revert the PR #10887.

[sachin-suresh-rapyuta]

Hi guys, Just wanted to check if there is any progress on this issue.

I updated the commit for this version 3.2.0-rc11.

Maybe I got it wrong, I tried to trigger this build twice for this version- 3.2.0-rc11 on RTD. The commit is still - b3cefebd which does not seem to update.

[stsewd]

@sachin-suresh-rapyuta you can try triggering a build on a different version for it to update the other versions.

[davidism]

I just ran into this with MarkupSafe. I have a 1.1.x tag pointing to the last commit on the 1.1.x line. I had to update that to address some docs theme changes. Force pushing the new tag did trigger a build of the 1.1.x version of the docs. But it checks out the commit by id rather than tag, and that id is still the commit the tag previously pointed to. https://app.readthedocs.org/projects/markupsafe/builds/25970674/ Triggering a build for a different version, then triggering a build for 1.1.x, did fix it, but this is very confusing. Why did the push trigger a build that didn't update the id?