Upgrading an instance results in "Skipped Errors"related for file m2m_sp_theme_css_include_b6b3b4a623232300fb0c949e27bf65d5.xmlDescriptionUpgrading an instance from Tokyo results in "Skipped Errors" for the file m2m_sp_theme_css_include_b6b3b4a623232300fb0c949e27bf65d5.xmlLogs will show entries like this example:2023-07-23 17:09:36 (824) worker.1 worker.1 txid=686cf1104e00 Skipping because file already exists with a different scope: update/m2m_sp_theme_css_include_b6b3b4a623232300fb0c949e27bf65d5.xmlSteps to Reproduce 1. Upgrade an instance where Content Publishing is installed2. Search sys_upgrade_history_log for the upgrade, and "Skipped Error"Observe the below error: 2023-07-23 17:09:36 (824) worker.1 worker.1 txid=686cf1104e00 Skipping because file already exists with a different scope: update/m2m_sp_theme_css_include_b6b3b4a623232300fb0c949e27bf65d5.xmlWorkaroundNo workaround neccesary, this error doesn't cause any functional issue and is fixed in the latest version of Content Publishing AppRelated Problem: PRB1687124