forked from angular/angular-cli
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build(deps): bump npm-registry-fetch from 4.0.3 to 4.0.7 in /integration/angular_cli #58
Merged
kadirselcuk
merged 1 commit into
renovate/angular
from
dependabot/npm_and_yarn/integration/angular_cli/npm-registry-fetch-4.0.7
Mar 24, 2021
Merged
build(deps): bump npm-registry-fetch from 4.0.3 to 4.0.7 in /integration/angular_cli #58
kadirselcuk
merged 1 commit into
renovate/angular
from
dependabot/npm_and_yarn/integration/angular_cli/npm-registry-fetch-4.0.7
Mar 24, 2021
Conversation
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
Bumps [npm-registry-fetch](https://github.com/npm/npm-registry-fetch) from 4.0.3 to 4.0.7. - [Release notes](https://github.com/npm/npm-registry-fetch/releases) - [Changelog](https://github.com/npm/npm-registry-fetch/blob/v4.0.7/CHANGELOG.md) - [Commits](npm/npm-registry-fetch@v4.0.3...v4.0.7) Signed-off-by: dependabot[bot] <support@github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps npm-registry-fetch from 4.0.3 to 4.0.7.
Changelog
Sourced from npm-registry-fetch's changelog.
Commits
d8df0b1
chore(release): 4.0.7110032b
fix: correct password redaction2275f55
chore(release): 4.0.6cd35987
fix: import URL from url module62ce833
chore(release): 4.0.543a5d84
chore: remove basic auth data from logs71ab0e7
chore(release): 4.0.4fc5d94c
Put default timeout back to zeroDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.