fix: use legacy-peer-deps for semantic-release process

[ZachJW34]

User facing changelog

na

Additional details

The npm-release job is broken due to peer-dependency issues. Before reverting the semantic-release dep (which has security implications), I'd like to try the NPM_CONFIG_LEGACY_PEER_DEPS option.

Link to latest master npm-release failure: https://app.circleci.com/pipelines/github/cypress-io/cypress/41450/workflows/e56453d4-5d77-4e96-8262-82517d9668aa/jobs/1716530

Steps to test

I have no good way to test this since semantic-release requires valid npm_tokens. The build is failing when running npm version but I can't reproduce this locally.

How has the user experience changed?

na

PR Tasks

• [na] Have tests been added/updated?
• [na] Has the original issue (or this PR, if no issue exists) been tagged with a release in ZenHub? (user-facing changes only)
• [na] Has a PR for user-facing changes been opened in cypress-documentation?
• [na] Have API changes been updated in the type definitions?

[cypress-bot]

Thanks for taking the time to open a PR!

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.
• Become familiar with the Code Review Checklist for guidelines on coding standards and what needs to be done before a PR can be merged.

[rachelruderman]

Here's hoping! 😸

[emilyrohrbough]

@ZachJW34 Do you have a link to the broken job?

[ZachJW34]

@emilyrohrbough updated the description with a link to the latest master build, I tried to fix it last week. All npm-release builds since the semantic-release bump have been failing (at least, the jobs that actually detect packages to publish)

[emilyrohrbough]

I have no good way to test this since semantic-release requires valid npm_tokens. The build is failing when running npm version but I can't reproduce this locally.

Could you update the script to perform a dry-run and test on this branch it provides the correct dry-run output?
https://github.com/semantic-release/semantic-release/blob/master/cli.js#L37

[ZachJW34]

@emilyrohrbough --dry-run passes locally, but it skips the semantic-release steps that are actually throwing the error

[lmiller1990]

let's give it a try

[cypress]

---

Test summary

37828 • 0 • 473 • 0 • 12

---

Run details

Project	cypress
Status	Passed
Commit	536e5cf
Started	Aug 9, 2022 10:56 PM
Ended	Aug 9, 2022 11:14 PM
Duration	17:50 💡
OS	Linux Debian - 11.3
Browser	Multiple

View run in Cypress Dashboard ➡️

---

Flakiness

	cypress/e2e/commands/xhr.cy.js		5
1	... > logs request + response headers
2	... > logs Method, Status, URL, and XHR
3	... > logs request + response headers
4	... > logs Method, Status, URL, and XHR
5	... > logs response
This comment includes only the first 5 flaky tests. See all 12 flaky tests in the Cypress Dashboard.

---

This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard