Config validation error in build.os. Value os not found

[derks]

Any help would be much appreciated... using pretty stock .readthedocs.yaml from the docs.

Details

• Read the Docs project URL: https://readthedocs.org/projects/cement/
• Build URL (if applicable): https://readthedocs.org/projects/cement/builds/23604160/
• Read the Docs username (if applicable): https://readthedocs.org/profiles/derks/

Expected Result

Successful build.

Actual Result

Error
Config validation error in build.os. Value os not found.

[stsewd]

Hi, you are missing using the build.os config value, see our docs for a quick start of a valid config file https://docs.readthedocs.io/en/stable/config-file/v2.html.

We should probably link to our docs when such errors appear.

[derks]

@stsewd thank you for the quick reply. Can you elaborate on what is not right in the .readthedocs.yaml configuration in the repo?

• https://github.com/datafolklabs/cement/blob/main/.readthedocs.yaml

[stsewd]

@derks looks like you have two cofig files https://github.com/datafolklabs/cement/blob/main/readthedocs.yml, you should delete the other one.

[derks]

Geeeeeeeeze.... not sure how I missed that :/. Thank you for the help... I'll try that now.

[derks]

@humitos thank you again for your help. I was able to fix main (latest) now... however I have having issues with building the 3.0 version (this is a Git tag). I tag 3, 3.0 every time I make a 3.0.x release, and this is the source for the 3.0 version. It seems that RTD is not pulling down the latest 3.0 tag, and therefore continues to fail.

Any insights? Is this a cache issue that will resolve itself, or is there anything we/I can do to force it along?

[stsewd]

@derks if you forced push the tag, you need to first build any other version for the commit to be updated first, after that you can trigger a build for it to pick the correct commit. See #10838.