Edouard Maleix

Looking at the logs, it appears that the `git push` step is skipped by `nx release`.

My bad, in the latest version, [Nx logs when pushing to Git](https://github.com/nrwl/nx/blob/master/packages/nx/src/command-line/release/changelog.ts#L267-L279), however in the Nx version used by code-pushup, it does not. Looking at the code used to push...

After further testing, it became clearer that there were some issues with the step to push commits in the `changelog` command. I upgraded to the latest Nx version (18.2.1), and...

> OK, if updating to Nx 18 helps, then let's do it. Do you want to create a PR? Or do you need some assistance? Since the changes were rather...

@robertsLando that's also what i would expect - #376

@EelcoLos this is quite typical behavior with NPM dependencies resolution. You could : - use Yarn - update the package.json in a PR

@AgentEnder, Thanks for reviewing. I noticed that the e2e tests have been failing for a while, and they are also blocking other PRs. Would you like some help fixing those...

It looks like the CI failure on merge was due to `nx format:check` failing, so I ran `nx format --all`. See https://cloud.nx.app/runs/PZ0uH8iPew

This would also be useful when using Ory Hydra as the OAuth2 authorization server. It is possible to create signed JWT but the default and recommended approach is using opaque...

@MarcialRosales When self-hosted, Ory Hydra is totally open. However, in more serious environments including in Ory Network (the product sold by the company maintaining Ory), the access is protected by...