feat: 'unsafe-to-chain-command' added as recommended rule

[Erik-Outreach]

No description provided.

[Erik-Outreach]

@BlueWinds did you have time to check on the deployment process and merging this extra PR? Please let me know if there's anything I can help with

[BlueWinds]

@BlueWinds did you have time to check on the deployment process and merging this extra PR? Please let me know if there's anything I can help with

I haven't had time to look into the deployment process. Going to see if anyone else on the team has some eyes to look into it.

[Erik-Outreach]

@BlueWinds did you have time to check on the deployment process and merging this extra PR? Please let me know if there's anything I can help with

I haven't had time to look into the deployment process. Going to see if anyone else on the team has some eyes to look into it.

@BlueWinds Did you find someone to have some eyes on it? It seems to me it's only some permission issue where the GH_TOKEN configured in CircleCI doesn't have the access to push changes in master: https://app.circleci.com/pipelines/github/cypress-io/eslint-plugin-cypress/127/workflows/2ccaa96c-c4ac-4613-9a40-bb75dc0eb9d9/jobs/512

[nagash77]

🎉 This PR is included in version 2.13.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[nagash77]

Hi @Erik-Outreach , thanks for the reminder. I took a look this morning and fixed the token issue and everything should be back on track.

[Erik-Outreach]

Hi @Erik-Outreach , thanks for the reminder. I took a look this morning and fixed the token issue and everything should be back on track.

Thank you! Unfortunately I might have missed one thing in my change and the latest release doesn't work. I'll push one more change shortly

[Erik-Outreach]

Hi @Erik-Outreach , thanks for the reminder. I took a look this morning and fixed the token issue and everything should be back on track.

Fix here: #126 - Apologises for the mistake