chore(deps): bump github.com/jedib0t/go-pretty/v6 from 6.7.8 to 6.7.9 in the minor-and-patch group#19
Conversation
Bumps the minor-and-patch group with 1 update: [github.com/jedib0t/go-pretty/v6](https://github.com/jedib0t/go-pretty). Updates `github.com/jedib0t/go-pretty/v6` from 6.7.8 to 6.7.9 - [Release notes](https://github.com/jedib0t/go-pretty/releases) - [Commits](jedib0t/go-pretty@v6.7.8...v6.7.9) --- updated-dependencies: - dependency-name: github.com/jedib0t/go-pretty/v6 dependency-version: 6.7.9 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: minor-and-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Greptile SummaryRoutine Dependabot patch bump of Confidence Score: 5/5Safe to merge — patch bump with no breaking changes and no code modifications. Only go.mod and go.sum are touched. The upstream patch fixes markdown table padding, a non-breaking improvement. No P0/P1 issues found. No files require special attention.
|
| Filename | Overview |
|---|---|
| go.mod | Bumps go-pretty/v6 from v6.7.8 to v6.7.9; no other dependency changes. |
| go.sum | Updates checksums for go-pretty/v6 v6.7.9; the go.mod hash is unchanged (as expected when only the upstream source changes), and the module source hash is correctly updated. |
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
A["go-pretty/v6 v6.7.8"] -->|"Patch bump"| B["go-pretty/v6 v6.7.9"]
B --> C["Fix: markdown table padding\n(jedib0t/go-pretty#402)"]
C --> D["printer/printer.go\n(markdown output format)"]
Reviews (1): Last reviewed commit: "chore(deps): bump github.com/jedib0t/go-..." | Re-trigger Greptile
|
Looks like github.com/jedib0t/go-pretty/v6 is updatable in another way, so this is no longer needed. |
Bumps the minor-and-patch group with 1 update: github.com/jedib0t/go-pretty/v6.
Updates
github.com/jedib0t/go-pretty/v6from 6.7.8 to 6.7.9Release notes
Sourced from github.com/jedib0t/go-pretty/v6's releases.
Commits
017a359table: markdown padding for human-friendly output; fixes #402 (#403)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 show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions