Dependabot 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)
- `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/quantonganh/blog/network/alerts).
:warning: We detected 7 security issues in this pull request:
Vulnerable Libraries (7)
Severity | Details
----- | --------
N/A | [pkg:golang/golang.org/x/net@v0.0.0-20220722155237-a158d28d115b@v0.0.0-20220722155237-a158d28d115b](https://github.com/quantonganh/blog/blob/4c65facc22a56fffa2d58dfbc29a26d11f69169a/go.sum#L482) upgrade to: *1.19.6,1.20.1,0.7.0*
N/A | [pkg:golang/golang.org/x/sys@v0.0.0-20201119102817-f84b799fce68@v0.0.0-20201119102817-f84b799fce68](https://github.com/quantonganh/blog/blob/4c65facc22a56fffa2d58dfbc29a26d11f69169a/go.sum#L519) upgrade to: *1.17.10,1.18.2,0.0.0-20220412211240-33da011f77ad*
High | [pkg:golang/golang.org/x/text@v0.3.7@v0.3.7](https://github.com/quantonganh/blog/blob/4c65facc22a56fffa2d58dfbc29a26d11f69169a/go.sum#L533) - **no patch available**
High | [pkg:golang/golang.org/x/crypto@v0.0.0-20210921155107-089bfa567519 @v0.0.0-20210921155107-089bfa567519 ](https://github.com/quantonganh/blog/blob/4c65facc22a56fffa2d58dfbc29a26d11f69169a/go.sum#L461) upgrade to: *0.0.0-20211202192323-5770296d904e*
High | [pkg:golang/golang.org/x/net@v0.0.0-20210226172049-e18ecbb05110@v0.0.0-20210226172049-e18ecbb05110](https://github.com/quantonganh/blog/blob/4c65facc22a56fffa2d58dfbc29a26d11f69169a/go.sum#L481) - **no patch available**
N/A | [pkg:golang/golang.org/x/sys@v0.0.0-20210615035016-665e8c7367d1@v0.0.0-20210615035016-665e8c7367d1](https://github.com/quantonganh/blog/blob/4c65facc22a56fffa2d58dfbc29a26d11f69169a/go.sum#L521) upgrade to: *1.17.10,1.18.2,0.0.0-20220412211240-33da011f77ad*
Medium | [pkg:golang/golang.org/x/crypto@v0.0.0-20210921155107-089bfa567519@v0.0.0-20210921155107-089bfa567519](https://github.com/quantonganh/blog/blob/4c65facc22a56fffa2d58dfbc29a26d11f69169a/go.sum#L461) - **no patch available**
More info on how to fix Vulnerable Libraries in [Go](https://docs.guardrails.io/docs/en/vulnerabilities/go/using_vulnerable_libraries.html?utm_source=ghpr).
Bumps golang.org/x/net from 0.0.0-20201021035429-f5854403a974 to 0.7.0.
Commits
Dependabot 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) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/quantonganh/blog/network/alerts).