FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

test: ensure npm version is not release candidate by MylesBorins · Pull Request #25538 · nodejs/node · GitHub

/ node Public

test: ensure npm version is not release candidate - #25538

Closed
MylesBorins wants to merge 1 commit into
nodejs:masterfrom
MylesBorins:no-npm-rc
Closed

test: ensure npm version is not release candidate#25538
MylesBorins wants to merge 1 commit into
nodejs:masterfrom
MylesBorins:no-npm-rc

Conversation

Copy link
Copy Markdown
Contributor

v11.6.0 ended up shipping with an npm version 6.5.0-next.0.
This test should avoid it happening in the future.

Copy link
Copy Markdown
Collaborator

nodejs-github-bot added the test Issues and PRs related to the tests. label Jan 16, 2019
Comment thread test/parallel/test-npm-version.js Outdated
Comment thread test/parallel/test-npm-version.js Outdated
Comment thread test/parallel/test-npm-version.js Outdated
Comment thread test/parallel/test-npm-version.js Outdated
Comment thread test/parallel/test-npm-version.js Outdated
Comment thread test/parallel/test-npm-version.js Outdated
Comment thread test/parallel/test-npm-version.js Outdated
MylesBorins force-pushed the no-npm-rc branch 2 times, most recently from 3fa37d5 to 0161c61 Compare January 16, 2019 23:15
v11.6.0 ended up shipping with an npm version `6.5.0-next.0`.
This test should avoid it happening in the future.

Copy link
Copy Markdown
Contributor Author

All feedback incorporated. PTAL

ljharb commented Jan 17, 2019

Copy link
Copy Markdown
Member

(linking to #25311 and #25234)

Copy link
Copy Markdown
Contributor Author

Copy link
Copy Markdown
Contributor Author

Landed in 2e613a9

MylesBorins added a commit that referenced this pull request Jan 18, 2019
v11.6.0 ended up shipping with an npm version `6.5.0-next.0`.
This test should avoid it happening in the future.

PR-URL: #25538
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Minwoo Jung <minwoo@nodesource.com>
);

const pkg = require(npmPathPackageJson);
assert(pkg.version.match(/^\d+\.\d+\.\d+$/),

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality
Suggested change
assert(pkg.version.match(/^\d+\.\d+\.\d+$/),
assert.ok(/^\d+.\d+.\d+$/.test(pkg.version.match),

addaleax pushed a commit that referenced this pull request Jan 23, 2019
v11.6.0 ended up shipping with an npm version `6.5.0-next.0`.
This test should avoid it happening in the future.

PR-URL: #25538
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Minwoo Jung <minwoo@nodesource.com>
MylesBorins mentioned this pull request Jan 24, 2019
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

test Issues and PRs related to the tests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants


Back | FazBrowse Home | New Git URL