allow same version when building npm package on Circle

[bahmutov]

• solves https://circleci.com/gh/cypress-io/cypress/182772 when we have not upgraded NEXT_DEV_VERSION on CircleCI after publishing new cypress NPM version

#!/bin/bash -eo pipefail
npm --no-git-tag-version version ${NEXT_DEV_VERSION:-0.0.0-development}
npm ERR! Version not changed, might want --allow-same-version

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2019-11-04T19_15_45_338Z-debug.log
Exited with code 1

Building a duplicate version is not a problem, since we control when we upload and release the official version.

[cypress-bot]

Thanks for the contribution! Below are some guidelines Cypress uses when doing PR reviews.

• Please write [WIP] in the title of your Pull Request if your PR is not ready for review - someone will review your PR as soon as the [WIP] is removed.
• Please familiarize yourself with the PR Review Checklist and feel free to make updates on your PR based on these guidelines.

PR Review Checklist

If any of the following requirements can't be met, leave a comment in the review selecting 'Request changes', otherwise 'Approve'.

User Experience

• The feature/bugfix is self-documenting from within the product.
• The change provides the end user with a way to fix their problem (no dead ends).

Functionality

• The code works and performs its intended function with the correct logic.
• Performance has been factored in (for example, the code cleans up after itself to not cause memory leaks).
• The code guards against edge cases and invalid input and has tests to cover it.

Maintainability

• The code is readable (too many nested 'if's are a bad sign).
• Names used for variables, methods, etc, clearly describe their function.
• The code is easy to understood and there are relevant comments explaining.
• New algorithms are documented in the code with link(s) to external docs (flowcharts, w3c, chrome, firefox).
• There are comments containing link(s) to the addressed issue (in tests and code).

Quality

• The change does not reimplement code.
• There's not a module from the ecosystem that should be used instead.
• There is no redundant or duplicate code.
• There are no irrelevant comments left in the code.
• Tests are testing the code’s intended functionality in the best way possible.

Internal

• The original issue has been tagged with a release in ZenHub.

[cypress]

---

Test summary

3474 • 0 • 46 • 0

---

Run details

Project	cypress
Status	Passed
Commit	6237b89
Started	Nov 4, 2019 10:15 PM
Ended	Nov 4, 2019 10:19 PM
Duration	03:55 💡
OS	Linux Debian - 9.8
Browser	Multiple

View run in 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

[bahmutov]

I have updated circle and appveyor to have NEXT_DEV_VERSION: 3.6.1