Cannot create CI/CD process for re-publishing Mesh

I'm trying to create CI/CD process for Mesh. So goal is to have Gitlab pipeline which triggers mesh update everytime mesh being updated in git repository.

By following documentation I can create CI/CD for deploying App Builder application and it works fine, but I cannot do the same for mesh.

Expected Behaviour

After I configured by Secrets,

aio api-mesh update mesh.json

Have to update mesh without using browser login again and again. Same as command

aio app deploy

So just to be clear, exactly same project, execute deploy command without asking for browser login, but mesh publish do - which makes impossible to implement CI/CD pipelines.

Actual Behaviour

aio api-mesh update mesh.json asking to login if run inside pipeline even if aio app deploy not

Steps to Reproduce

1. Create New App Builder application
2. deploy application with aio app deploy
3. Application successfully deployed.
4. Run any aio api-mesh create mesh.json command
5. You will be forced to login via browser.

Logs taken while reproducing problem

Some notes: I see that mesh plugin has own auth helpers:

@adobe/aio-cli/node_modules/@adobe/aio-cli-plugin-api-mesh/src/helpers.js

which maybe working in different manner then default auth mechanism.

Beginne mit @adobe/aio-cli/node_modules/@adobe/aio-cli-plugin-api-mesh/src/helpers.js und vergleiche dessen Authentifizierungspfad mit dem von aio app deploy verwendeten. Reproduziere aio api-mesh create mesh.json und aio api-mesh update mesh.json im beschriebenen GitLab-Pipeline-Kontext. Erledigt ist dies, wenn die Mesh-Befehle die konfigurierten Secrets verwenden, ohne eine weitere Browser-Anmeldung zu erfordern, und eine Testabdeckung für den Pipeline-Fall vorhanden ist.