If Flutter is keen on having this fix, it is found in dartdoc 6.1.5, cc @goderbauer @gspencergoog

@srawlins Consider cherry-picking 6.1.5 to beta if it's still possible. This also affects the SDK docs (and users who generate with dart doc) and it's a little awkward.

@parlough is api.dartdoc.dev really generated strictly from the dartdoc that is in the SDK? I hoped it was completely detached, like pub.dev is.

@srawlins It looks like it is generated as part of the release infrastructure with the dartdoc in third_party/pkg: https://dart.googlesource.com/recipes/+/refs/heads/main/recipes/release/sdk.py#155

I'm not super familiar with the SDK setup or those recipes, but I guess that should be the same one as in DEPS?

\cc @sortie who may know more specifics.

@srawlins – I do believe it's based on the SDK dep. Went through this churn last time we rolled dartdoc

CC @devoncarew RE rolling DEPS

Yeah, the api.dart.dev documentation is built by the sdk recipe. It uses the Dart SDK that was just freshly build invoked on third_party/pkg/dartdoc/bin/dartdoc.dart to generate the dartdocs, which are then uploaded to cloud storage, which is then automatically served by api.dart.dev. Notably the documentation for older releases is not regenerated and remain as it was permanently. I hope that answers your questions :)

Thanks! Maybe I can cherry-pick one line in a DEPS roll CL