Welcome to mirror list, hosted at ThFree Co, Russian Federation.

github.com/npm/cli.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2022-09-22chore(ci): use globally installed npm executable (#5555)Luke Karrys
2022-09-22chore(ci): rebuild cmark-gfm only before testsLuke Karrys
2022-09-22chore(ci): run link before testingLuke Karrys
2022-09-20chore: apply template-oss changesLuke Karrys
2022-09-15chore: template-oss@4.1.2Luke Karrys
2022-09-08feat(workspaces): update supported node engines in package.json (#5485)Luke Karrys
BREAKING CHANGE: all workspace packages are now compatible with the following semver range for node: `^14.17.0 || ^16.13.0 || >=18.0.0`
2022-09-08feat: update supported node engines in package.jsonGar
This also replaces the previous check for known broken versions of node with an exception handler for syntax errors in order to try and give a nicer error message when attempting to run npm on older node versions. BREAKING CHANGE: `npm` is now compatible with the following semver range for node: `^14.17.0 || ^16.13.0 || >=18.0.0` Ref: npm/statusboard#519
2022-09-02chore: @npmcli/template-oss@3.8.1 (#5461)Luke Karrys
2022-08-31chore: use release pleaseLuke Karrys
2022-08-26chore: @npmcli/template-oss@3.7.1Luke Karrys
2022-08-26chore: @npmcli/template-oss@3.7.0Luke Karrys
2022-06-22chore: rename node branches (#5028)Gar
Both nodejs and npm branches are now "main"
2022-06-01chore: merge benchmark action to single job (#4970)Luke Karrys
2022-05-25chore(benchmarks): fix secret name in benchmark workflows (#4936)nlf
2022-05-11chore: @npmcli/template-oss@3.5.0 (#4882)Gar
2022-05-10chore: update action secrets + bot info (#4878)nlf
* chore: update bot account and secrets for nodejs/node updates * chore: update bot account and secrets for npm/benchmarks triggers * chore: add npm CLI robot to mailmap and exclude from AUTHORS
2022-05-03chore(benchmarks): add missing space to if condition (#4841)nlf
2022-04-26chore(deps): @npmcli/template-oss@3.4.2Luke Karrys
2022-04-26chore(benchmark): add comment permission check and filter paths (#4766)Luke Karrys
The updates the issue comment check in the benchmark script, so it only will trigger if posted by a user with admin rights to the repo. It also changes the comment to trigger it to `@npm-robot benchmark this` For pull requests, it now limits benchmarks only when the files changed include something inside `lib/`. Requires https://github.com/npm/benchmarks/pull/30 to be merged in the benchmark repo to allow `issue_comment` as a valid trigger.
2022-04-20chore: fix nodejs pr actionLuke Karrys
2022-04-15chore: fix benchmark script syntaxLuke Karrys
You cannot use a secret as part of an if expression in actions
2022-04-14chore: refactor and update actions in nodejs pr workflowLuke Karrys
2022-04-14chore: consolidate and refactor benchmark workflows (#4715)Luke Karrys
2022-04-14chore: add release github actionLuke Karrys
2022-04-14chore: do less smoke testing on every commitLuke Karrys
2022-04-07chore: @npmcli/template-oss@3.3.2 (#4694)Gar
2022-04-07chore: @npmcli/template-oss@3.3.1 (#4692)Gar
2022-03-30deps: @npmcli/template-oss@3.2.2 (#4639)Luke Karrys
- add some basic tests for docs - make dockhand script work on windows - cleanup main CI to match template-oss - add a git status check for cli ci tests - use resetdeps for ci steps
2022-03-30deps: @npmcli/template-oss@3.2.1Luke Karrys
- `no-shadow` was disabled for the cli and arborist due to the amount of changes required. These should be fixed later. - Manually updated linting in the cli root to match closer to what template-oss does - Included docs to be managed with template-oss. This required adding an empty test for now, with the plan to add real tests later.
2022-03-24fix: 100% coverage in tests (#4607)Gar
* fix: 100% coverage in tests * Removed dead code in `lib/utils/usage.js`. * Removed dead code in `lib/base-command.js`. * Removed "load-all" test, we currently have 100% coverage and new PRs without tests will be rejected if they don't add coverage for new files. * Removed `check-coverage` script as a separate command. * Removed separate coverage test in ci.yml. * Removed `coverage` flag from tap config, the default is already to enforce 100% coverage. Removed a tiny bit of dead code resulting from this * fix: clean up usage output Removed usage lib, rolled logic into base-command.js Cleaned up usage output to be less redundant
2022-03-02chore: @npmcli/template-oss@2.9.2 (#4491)Gar
Should get release-please working in workspaces
2022-03-02chore: @npmcli/template-oss@2.9.1Gar
2022-01-26chore: add docs issue templates (#4321)gar/docs-backportTierney Cyren
2022-01-11fix: added arborist action and updated template-oss (#4215)Nathan Fritz
- updated template-oss and manually added arborist ci - updated arborist ci to include path - fixed workspace reference and upgraded template-oss - upgraded template-oss properly
2022-01-05chore: update bug_8 environment (#4156)fncolon
Guiding how to update the environment in bug pull request much clear.
2021-12-16Bring in all libnpm modules + arborist as workspaces (#4166)Nathan Fritz
Added libnpm workspaces and arborist
2021-12-09chore(benchmarks): tidy up benchmark workflowsnlf
PR-URL: https://github.com/npm/cli/pull/4145 Credit: @nlf Close: #4145 Reviewed-by: @wraithgar
2021-12-09chore(ci): fix license validation CI step nameFelipe Plets
PR-URL: https://github.com/npm/cli/pull/4118 Credit: @felipeplets Close: #4118 Reviewed-by: @darcyclarke
2021-11-18separate github actions for workspacesNathan Fritz
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
2021-11-03chore: update issue template env with npm configLuke Karrys
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
2021-11-03chore(ci): update setup-node action to v2 and enable cachenlf
PR-URL: https://github.com/npm/cli/pull/3958 Credit: @nlf Close: #3958 Reviewed-by: @wraithgar
2021-11-03chore: limit CI buildsGar
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
2021-11-02chore: add latest npm check to bug templateGar
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
2021-10-11chore: update bug template to reference latest versionDarcy Clarke
PR-URL: https://github.com/npm/cli/pull/3857 Credit: @darcyclarke Close: #3857 Reviewed-by: @wraithgar
2021-10-11chore: update issue configsDarcy Clarke
PR-URL: https://github.com/npm/cli/pull/3858 Credit: @darcyclarke Close: #3858 Reviewed-by: @wraithgar
2021-10-07feat: drop node 10, 11, and programmatic apiGar
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
2021-10-07chore: replace npm support with GitHub communityMyles Borins
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
2021-08-17chore(ci): check that docs are up to date in ciisaacs
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
2021-07-15chore: use better name on nodejs commitsRuy Adorno
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
2021-06-11chore(libnpmdiff): added as workspaceRuy Adorno
- 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