This document describes frequently asked questions and their answers. If your question is not listed or you still need help, contact the MDN team on chat.mozilla.org#mdn or write to us on Discourse.
Once a pull request is merged to update BCD, it takes a week or two for a new version of the repository to be released, and then a few days for it to launch on MDN. The process is:
-
A pull request is reviewed and merged to
main
. -
Project owners publish a new release of
@mdn/browser-compat-data
. See Publishing a new version of@mdn/browser-compat-data
for details. -
MDN staff merge a pull request that updates the BCD version in Yari, the MDN engine. This typically happens within a day of the release of the npm package.
-
Tables are then generated on MDN Web Docs:
- Existing compatibility tables will automatically update.
- For new pages, or for pages without existing compatibility tables, you must add the
{{Compat}}
macro and thebrowser-compat
front-matter key to the page. For instructions, see Inserting the data into MDN pages.
Sorry for the wait. Many outside factors, such as our other projects, may grab our attention and slow BCD PR reviews. If it has been more than a month and there has been no response from a reviewer, please feel free to ping one of us and request a review. You can find a list of peers and owners in the governance doc.
Of course! If we have requested more information from you (the pull request author) and do not hear back from you in two months, we will close the PR. You are more than welcome to reopen the PR and address the feedback at any time.
If the PR has been closed due to inactivity, you may open a new PR to supersede it. Please do not open a new PR if the existing PR has not been closed.