Hi @rebloor -- this PR should not have been merged yet if there was a failing test, as BCD requires CI tests to pass before merging.

I removed the MDN URLs that were causing the CI to fail in #23793. The new MDN URL linter should automatically add these back once the mdn-content-inventory has been updated and includes the information about the new pages.

@queengooborg I wasn't aware of the linter behavior regarding the addition of URLs once documentation is published. Where would I have found information about this new behavior? So, from now on, for new docs, I shouldn't include the "mdn_url" but wait for them to be added automatically.

Sorry for not responding to this earlier, this got buried in my notifications.

New linter behavior isn't something that we've documented in BCD, as it is an internal change that impacts contributors, not consumers. (Actually, hardly any specific linter rules are documented; only the ones that were originally non-linted policies are documented.) New linter rules are, however, almost always discussed during the BCD weekly calls and aren't implemented before they receive owner consensus.

The motivation for the new MDN URL linter is to reduce the need for manual updates to MDN URLs when pages are created, moved or deleted. So far, it's been mostly helpful, though this is a case where it hasn't been quite so helpful (the pages were updated but the linter didn't have the updated information yet -- which is why I brought up the idea of making the URL linter warn instead of error).

The important part is just making sure that the CI always returns good before merging a PR, even if the issue will eventually fix itself when dependencies are updated. This is because unlike MDN content, the CI tests for PRs run on EVERY file, not just the ones that are modified. Thus, if a PR with a failing test is merged, all other open PRs suddenly have failing tests, which halts all BCD development until the CI passes again!

@queengooborg thanks for that, should I come across another similar issue I'll check with you first rather than assuming it's an issue that would be otherwise fixed. (Are there minutes from the weekly call? Something I could search if I do come across the situations.)

There are meeting notes, yes! Here they are: https://docs.google.com/document/d/e/2PACX-1vS8QeLHJNMAohmVLDLM0d-6EYo1H5Pw95xz9BFHmkmLWoj80H19XZVJdzYvd2YPig6CaC-8x7lpQm9W/pub