Age | Commit message (Collapse) | Author |
|
PR-URL: https://github.com/npm/cli/pull/4145
Credit: @nlf
Close: #4145
Reviewed-by: @wraithgar
|
|
PR-URL: https://github.com/npm/cli/pull/4118
Credit: @felipeplets
Close: #4118
Reviewed-by: @darcyclarke
|
|
PR-URL: https://github.com/npm/cli/pull/4050
Credit: @fritzy
Close: #4050
Reviewed-by: @wraithgar
PR-URL: https://github.com/npm/cli/pull/4050
Credit: @fritzy
Close: #4050
Reviewed-by: @wraithgar
|
|
Also update with other items from template-oss
PR-URL: https://github.com/npm/cli/pull/3982
Credit: @lukekarrys
Close: #3982
Reviewed-by: @wraithgar
PR-URL: https://github.com/npm/cli/pull/3982
Credit: @lukekarrys
Close: #3982
Reviewed-by: @wraithgar
PR-URL: https://github.com/npm/cli/pull/3982
Credit: @lukekarrys
Close: #3982
Reviewed-by: @wraithgar
|
|
PR-URL: https://github.com/npm/cli/pull/3958
Credit: @nlf
Close: #3958
Reviewed-by: @wraithgar
|
|
We don't need duplicate builds on pull requests and pushes. This should
cut our actions essentially down to half of what they are now.
PR-URL: https://github.com/npm/cli/pull/3981
Credit: @wraithgar
Close: #3981
Reviewed-by: @darcyclarke
|
|
Adds a new required checkbox to our bug template directing people to use
the latest npm version to verify their bug still exists.
PR-URL: https://github.com/npm/cli/pull/3977
Credit: @wraithgar
Close: #3977
Reviewed-by: @darcyclarke
|
|
PR-URL: https://github.com/npm/cli/pull/3857
Credit: @darcyclarke
Close: #3857
Reviewed-by: @wraithgar
|
|
PR-URL: https://github.com/npm/cli/pull/3858
Credit: @darcyclarke
Close: #3858
Reviewed-by: @wraithgar
|
|
BREAKING CHANGE:
- Drop official support for node versions less than v12.
- Drop support for `require('npm')`
- Update a few subdependencies that dropped node10 support, and brought
in the latest node-gyp
PR-URL: https://github.com/npm/cli/pull/3762
Credit: @wraithgar
Close: #3762
Reviewed-by: @fritzy
|
|
for general support we are now direct folks to github.community not general
npm support
PR-URL: https://github.com/npm/cli/pull/3850
Credit: @MylesBorins
Close: #3850
Reviewed-by: @wraithgar
|
|
When we accidentally edit the auto-generated portions of the docs, this
will catch the error and cause CI to fail.
Later phase automated safety check that the early-stage human commenting
in the last commit also addresses.
Re: #3654
Re: #3630
PR-URL: https://github.com/npm/cli/pull/3655
Credit: @isaacs
Close: #3655
Reviewed-by: @nlf
|
|
Currently, the name: `npm-robot` is being used in nodejs changelogs as
the atttribution author name for npm-update commits. This makes it so
that entries in the changelog referring to our updates reads like:
```
upgrade npm to 7.18.1 (npm-robot) #39065
```
This change makes it so that the name used in commits is `npm team`,
this way the changelogs entry should read instead as:
```
upgrade npm to 7.18.1 (npm team) #39065
```
Ref: https://nodejs.org/en/blog/release/v16.4.0/
PR-URL: https://github.com/npm/cli/pull/3541
Credit: @ruyadorno
Close: #3541
Reviewed-by: @wraithgar, @targos, @BethGriggs
|
|
- Setup ./packages/* as workspaces
- Moved source from: https://github.com/npm/libnpmdiff to
./packages/libnpmdiff
- Added CI target for workspaces
Relates to: https://github.com/npm/statusboard/issues/362
PR-URL: https://github.com/npm/cli/pull/3386
Credit: @ruyadorno
Close: #3386
Reviewed-by: @wraithgar
|
|
* fix: add git remote pull
* wip: update workflow
* wip: update to npm/node
* wip: upstream sync
* wip: revert standard pull
* wip: revert to nodejs/node
|
|
PR-URL: https://github.com/npm/cli/pull/3344
Credit: @gimli01
Close: #3344
Reviewed-by: @darcyclarke
|
|
|
|
* chore: deps workflow
* wip: test
* wip: test
* wip: test
* wip: update repo to nodejs/node
* wip: add jq parser
|
|
PR-URL: https://github.com/npm/cli/pull/3324
Credit: @gimli01
Close: #3324
Reviewed-by: @wraithgar
|
|
Moves workflow to create NPM CLI dependency pull request from npm/node.
Adds input to workflow dispatch trigger
PR-URL: https://github.com/npm/cli/pull/3294
Credit: @gimli01
Close: #3294
Reviewed-by: @darcyclarke
|
|
PR-URL: https://github.com/npm/cli/pull/3206
Credit: @lukehefson
Close: #3206
Reviewed-by: @darcyclarke
|
|
Lightweight smoke test suite that runs common commands so that we can
also have a holistic check during CI.
PR-URL: https://github.com/npm/cli/pull/2959
Credit: @ruyadorno
Close: #2959
Reviewed-by: @nlf
|
|
PR-URL: https://github.com/npm/cli/pull/2869
Credit: @jansepke
Close: #2869
Reviewed-by: @wraithgar
|
|
|
|
|
|
In this node version, fall back to `util.promisify` of the callback version.
Maybe fixes https://github.com/npm/cli/issues/2623. Maybe fixes https://github.com/npm/cli/issues/2652. Maybe fixes https://github.com/npm/cli/issues/2625.
PR-URL: https://github.com/npm/cli/pull/2654
Credit: @ljharb
Close: #2654
Reviewed-by: @wraithgar, @ruyadorno
|
|
PR-URL: https://github.com/npm/cli/pull/2682
Credit: @ljharb
Close: #2682
Reviewed-by: @wraithgar
|
|
|
|
|
|
- fix prune target
- fix ci build
- run rebuild after install
PR-URL: https://github.com/npm/cli/pull/2068
Credit: @nlf
Close: #2068
Reviewed-by: @ruyadorno
|
|
|
|
We are targetting 100% test coverage for npm v7 GA. Using a
coverage-map, we require that any of the newly created tests fully cover
the module that they are testing. However, this has the side effect of
_always_ hitting 100% coverage when running 'npm test', even though not
all modules are being tested.
This adds a new 'load-all' test which, in 'check-coverage' mode, tells
nyc to include every file in the project.
This also removes the double-run of our tests in CI, where we run once
and then immediately run the same exact thing again for Coveralls, and
sends the 'check-coverage' output to Coveralls instead.
PR-URL: https://github.com/npm/cli/pull/1820
Credit: @isaacs
Close: #1820
Reviewed-by: @ruyadorno
|
|
Accidentally landed this in the v7 branch, didn't realize it was based on v6.
|
|
Update the matrix to have two Windows workflows: one running PowerShell
and one running bash.
|
|
|
|
|
|
|
|
|
|
|
|
trigger benchmark suite
|
|
|
|
This should be more consistent since it should use the specified standard version and not the latest one.
PR-URL: https://github.com/npm/cli/pull/604
Credit: @XhmikosR
Close: #604
Reviewed-by: @mikemimik
|
|
- Moved windows builds to travis-only since they're currently failing
on GHA and it's not code-related
- Added setup on GHA config to only run coverage once in ubuntu target
|
|
PR-URL: https://github.com/npm/cli/pull/600
Credit: @XhmikosR
Close: #600
Reviewed-by: @ruyadorno
|
|
This will allow all builds to run even if one fails
PR-URL: https://github.com/npm/cli/pull/601
Credit: @XhmikosR
Close: #601
Reviewed-by: @ruyadorno
|
|
PR-URL: https://github.com/npm/cli/pull/278
Credit: @mikemimik
Close: #278
Reviewed-by: @claudiahdz
|
|
- This will ensure we inherit our standard labels from the `open-source-project-boilerplate`
PR-URL: https://github.com/npm/cli/pull/282
Credit: @darcyclarke
Close: #282
Reviewed-by: @ruyadorno
|
|
PR-URL: https://github.com/npm/cli/pull/272
Credit: @JasonEtco
Close: #272
Reviewed-by: @ruyadorno
|
|
Refs: https://github.com/npm/cli/pull/5
PR-URL: https://github.com/npm/cli/pull/17/
Credit: @watilde
Reviewed-By: @zkat
|
|
`npm is doing something I don't understand.` is often inappropriately used when the author means `npm is producing incorrect or undesirable behavior.`. I only had to look thru the first page of open issues to find 5 examples of this.
PR-URL: https://github.com/npm/npm/pull/19893
Credit: @MrStonedOne
Reviewed-By: @zkat
|