semantic-release fails

[MikeMcC399]

Situation

• The script "semantic-release": "semantic-release pre && npm publish --access public && semantic-release post" in package.json fails:

  Too many non-option arguments: got 1, maximum of 0

• Running npx semantic-release directly results in the error:

  An error occurred while running semantic-release: TypeError: os.tmpDir is not a function

• The configured version semantic-release@17.2.3 was released on Nov 16, 2020

• The workflow .github/workflows/main.yml has disabled semantic-release by commenting it out:

commit-info/.github/workflows/main.yml

Lines 14 to 15 in 1147690

	# - if: github.ref == 'refs/heads/master'
	# run: npm run semantic-release

Assessment

• Renovate PR chore(deps): update dependency semantic-release to version 17.2.3 🌟 #115 auto-updated from semantic-release@8.2.3 to semantic-release@17.2.3 to resolve a vulnerability issue. It did not however migrate the script accordingly.

• semantic-release@9.0.0 was a breaking change with a migration guide content:

  Update the semantic-release in your package.json from:

  "scripts": {
    "semantic-release": "semantic-release pre && npm publish && semantic-release post"
  }

  To:

  "scripts": {
    "semantic-release": "semantic-release"

• The error "TypeError: os.tmpDir is not a function" results from the use of the outdated dependency dont-crack

Suggestion

• Rework the use of semantic-release
• Update to latest version
• Use standard plugins as far as possible

[MikeMcC399]

@jennifer-shehane

• There are multiple issues in this repo (see also devDependencies review #164) and the situation is similar to https://github.com/cypress-io/get-windows-proxy that was addressed a couple of weeks ago.

• I assume that since this repo is important for Cypress Cloud that it makes sense to keep it up to date. If the Cypress.io team can handle corresponding PRs, I can submit PRs to propose fixing the issues. I already made a start, but I wouldn't want to submit more without there being some feedback.