It looks like the new Edge will be powered by Blink 79 and it will be released in January: https://blogs.windows.com/msedgedev/2019/11/04/edge-chromium-release-candidate-get-ready/

In order to update our data, the idea is to use the current "edge" browser and add new versions to it. Currently, we have versions 12 to 18: https://github.com/mdn/browser-compat-data/blob/master/browsers/edge.json

We would then add version 79 as the subsequent version to Edge 18:

"79": {
  "release_date": "2020-01-15",
  "release_notes": "https://docs.microsoft.com/en-us/something",
  "status": "current",
  "engine": "Blink",
  "engine_version": "79"
}

Further, we will need to mass update the Edge compat data:

• Update to version 79 if a feature is supported in Chrome and is not already supported in Edge 12 to 18.
• Add a new range stating "false" if a feature is supported in Edge 12 to 18 but is no longer supported in Chrome 79.
• Other edge (ha!) cases, that we need to think about?!

Work for a mirroring script has been started in #4729. It needs to be reviewed and then we need to create a migration to perform this mass-update.

@kypflug how does this plan sound to you? Are you okay with "79" (and following) appearing as version numbers for Edge in MDN and caniuse compat tables?