Permalink
Show file tree
Hide file tree
1 comment
on commit
sign in to comment.
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
chore: updated node-fetch version to 2.6.7 (#124)
* chore: updated node-fetch version to 2.6.7 * build: use node 16.x instead of 15.x
- Loading branch information
1 parent
efed703
commit a3b3a94
Showing
2 changed files
with
2 additions
and
2 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
a3b3a94There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any good reasons why the version numbers are pinned (which prevents some security and patch updates)?
Them SemVer selector
^should be not problematic.Besides this, if you want to pin the version of all dependencies and their dependencies, there is npm-shrinkwrap. Otherwise users would have to install with
npm i cross-fetch --save-exactor similar. See also https://docs.npmjs.com/cli/v6/commands/npm-install