Varun Sharma

Hi @MTRNord, I have added a limitations section in the readme that states that harden-runner is only supported for GitHub-hosted runner (Ubuntu VM). We do not have plans to support...

@h0x0er can you please investigate this?

Thanks for the info!

I think it has to do with `problem_matchers`. Try to find out more about them. https://github.com/erlef/setup-beam/blob/69fb25ba7e2c546dfc085871ecf2fc5382c9843d/src/setup-beam.js#L79 If you set `disable_problem_matchers ` to true, see if the issue goes away?

So we need to understand how to disable problem_matchers when post harden-runner step starts. Or may be there is a bug in the way they have enabled it, so the...

Hi @miguelnietoa, I noticed that you added a wildcard to the allowed endpoint for Azure storage. https://github.com/kommitters/editorjs-toggle-block/commit/d69e475439f02ac85eb47ac1311e6e66cb74daf9 `harden-runner` does not support wildcards in domain names. As a result, harden-runner is...

Thanks @miguelnietoa! We are working on a change where in the future harden-runner will automatically detect the cache endpoint. So then it will work fine on forks as well and...

Hi @miguelnietoa, I forgot to update you on the original issue. The reason the `harden-runner` logs were showing as warnings is because `erlef/setup-beam` (erlef/setup-elixir has been renamed I believe to...

Thanks @miguelnietoa! I will go ahead and close the issue.

linked to https://github.com/step-security/secure-workflows/issues/65