Uncommitted sys_app change after publishing new application version

[Nico Kampf]

Hi together,
I got a couple of Custom and Customized Applications in Servicenow, which are linked to Source Control (git).
Whenever I publish a new App-Version via the Servicenow Studio, an uncommitted change of the type "Custom Application [sys_app]" gets created in the default Update Set of the application.
As far as I can see, this updates the store_correlation_id, sys_mod_count and the date on which the Application was updated (sys_updated_on) in the sys_app.
Is this an intentional behavior?
If so, why is this change not committed with the publish, but only exists locally on the instance?
Thank you in advance!

[Thomas Weyer]

Hello.  I am experiencing the same issue in Yokohama Patch 1.

All changes committed via Studio
Attempt to Publish in ServiceNow Studio - specifying a new version number
The pipeline request is created and immediately cancelled-failed with this error:
Error: There are changes that must be committed or stashed before this application can be published. For more information, please see the documentation.

I believe after specifying a new version number, the sys_app record is updated and therefore a newly uncommitted change. 

Only workaround is to fall back to Studio for publishing and not harness the pipeline.