Mike McCready

@kostiantynvoiku It's good to hear you were able to solve your issue! Thanks for your feedback!

@kostiantynvoiku I'm sorry to hear that you are hit with the same issue again. Looking at the information provided I don't see the reason for your problem, so I suggest...

@saeta-eth - The action does not explicity support pnpm workspaces and this issue is most probably caused by the combination of custom workflows with caching and the action's caching. So...

@kostiantynvoiku - If it is working for you with the addition of `pnpm cypress install` in your workflow that is probably the best we can expect at this time considering...

I'm going to close this issue now. The recommendation remains that if you are having problems with caching using pnpm, the easiest workaround is to add the following into the...

`tslint` is still in use in the repo, as shown by the Dependency Dashboard:

Partial resolution through: - PR #32343 - PR #32566

@irbrad Could you please post your workflow?

@irbrad Please refer to the GitHub Actions documentation [steps context](https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/accessing-contextual-information-about-workflow-runs#steps-context) together with [jobs..steps[*].continue-on-error](https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/accessing-contextual-information-about-workflow-runs#steps-context) When a `continue-on-error` step fails, the `outcome` is `failure`, but the final `conclusion` is `success`. This is...

@irbrad Could you please provide some screenshots to illustrate what checkmarks you are referring to? Is your repo public or private?