Upgrade: Bump github.com/jedib0t/go-pretty/v6 from 6.5.8 to 6.5.9 #70
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [github.com/jedib0t/go-pretty/v6](https://github.com/jedib0t/go-pretty) from 6.5.8 to 6.5.9. - [Release notes](https://github.com/jedib0t/go-pretty/releases) - [Commits](jedib0t/go-pretty@v6.5.8...v6.5.9) --- updated-dependencies: - dependency-name: github.com/jedib0t/go-pretty/v6 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
|
Hi there 👋, @DryRunSecurity here, below is a summary of our analysis and findings.
Note 🟢 Risk threshold not exceeded. Change Summary (click to expand)The following is a summary of changes in this pull request made by me, your security buddy 🤖. Summary: The changes in this pull request are focused on updating the versions of dependencies used in the Go project. Specifically, the version of the However, it is always a good practice to review the changelog or release notes of the updated dependency to ensure that there are no security-related changes or fixes included in the new version. This can help identify any potential security implications of the update. Additionally, having a comprehensive testing suite and a robust security review process in place is recommended to catch any potential security issues introduced by dependency updates or other code changes. Files Changed:
Powered by DryRun Security |
Vulnerable Libraries (1)
More info on how to fix Vulnerable Libraries in Go. 👉 Go to the dashboard for detailed results. 📥 Happy? Share your feedback with us. |
santoshkal
deleted the
dependabot/go_modules/github.com/jedib0t/go-pretty/v6-6.5.9
branch
Bumps github.com/jedib0t/go-pretty/v6 from 6.5.8 to 6.5.9.
Release notes
Sourced from github.com/jedib0t/go-pretty/v6's releases.
Commits
b0affc2table: update note about auto-merge (#320)5395a20table: html row automerge support (#319)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)