Unfortunately parsing the code is a very time intensive task even if done with wp cli.
Thus, we cannot do that online on the live server.
We have to install a local copy of the site, an exact 1:1 copy. Then we have to run the parser (obviously using the latest, updated stable CP version). That will regenerate the Code Reference.
Then we can export and import those with an import tool I have installed on the live site.
This is the current process. It can only be done after the actual stable release is out (in other words, once CP is available as a stable release 1.3.0 in this case, and the master of git is been updated with that as well.)
If it where so that zero line numbers of the code changed whatsoever then we would not need to do this process. (I mean: code may change, but position in file could stay the same).
But this is almost never the case, thus the process needs to be run at least each “major” update of CP (which luckily there aren’t that many).
After the first re-import of data from local parser to online site, technically, we wont have to re-import the whole bunch of code ref’s anymore next time but only those which changed since lasts export/import. This however assumes that we use the import tool I tested and none other (at least, I do not know of any other import tool that has this feature)
WP Itself solves that with jetpack and some cron events etc, which is basically the same, just more distributed and thus also more complex.
However, be it how it is, we will not have to keep track of the changes made in code.
The parser will do this all for us. We just need to re-run it and re-import things using a 1:1 copy of the live site, that’s it.