After publishing a changeset, the changeset sometimes still appears as if it's unpublished for one page load

After you publish a changeset, sometimes you will see that on the initial page load after the publishing happens, the changeset is still presented on the screen as though it were unpublished.

I think this is more likely to happen on sites that have a lot of CPS content where the publishing process takes a while to finish.

It appears to be due to a race condition involving the database transaction that is used during publishing and the code that notifies the client that the changeset was published.