Manuel Kaufmann

> Also, we need to check the settings in [readthedocs/readthedocs-ops](https://github.com/readthedocs/readthedocs-ops) and [readthedocs/readthedocs-corporate-ops](https://github.com/readthedocs/readthedocs-corporate-ops) and migrate them as well. @copilot can you do that? I checked in -ops repositories and opened: -...

We can merge this after today's deploy, so we have a full week to test it locally just in case.

Well, we didn't merge this for this deploy, but that's fine. We don't want to deal with Celery issues during Xmas 😄 . I add this PR to one of...

`minPropertires: 1` looks correct to me. It doesn't make sense to have `build.tools: {}` since it does nothing and only adds confusion.

You can use `build.jobs` or `build.commands` as described in https://docs.readthedocs.com/platform/latest/build-customization.html to build your docs with Zensical. If you have a project already working, please give it a try and let...

> I suspect this happens because the `schema.json` lives in the source code repository. When a PR merging support for a new Python version is merged, the schema updates immediately...

Yes. There is a lag between we merge PRs and deploy the changes to production. rel branch will have the minimum of that time.

Do you know how to reproduce this? I tried triggering a build for the same version twice and the first build was cancelled automatically successfully. I also tried cancelling the...

Hi, I've thought a little about this and found a few issues that we will hit here. One of them is something we have struggled in the past already: _"it's...

It seems the fix we deployed for `Build.healthcheck` worked. We have only a few builds in invalid states now: ``` ## Community In [2]: from readthedocs.builds.constants import BUILD_FINAL_STATES In [6]:...