build(deps): Bump github.com/mgechev/revive from 1.3.7 to 1.3.9 #2576
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [github.com/mgechev/revive](https://github.com/mgechev/revive) from 1.3.7 to 1.3.9. - [Release notes](https://github.com/mgechev/revive/releases) - [Changelog](https://github.com/mgechev/revive/blob/master/.goreleaser.yml) - [Commits](mgechev/revive@v1.3.7...v1.3.9) --- updated-dependencies: - dependency-name: github.com/mgechev/revive dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
|
Warning Rate limit exceeded@gsk967 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 11 minutes and 41 seconds before requesting another review. How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. WalkthroughThe recent updates to the Changes
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files ignored due to path filters (1)
go.sumis excluded by!**/*.sum
Files selected for processing (1)
- go.mod (5 hunks)
Additional comments not posted (11)
go.mod (11)
24-24: Verify compatibility with Go 1.22.The update to
github.com/mgechev/revivefromv1.3.7tov1.3.9includes dropping support for Go 1.20 and adding support for Go 1.22. Ensure that the project is compatible with Go 1.22.Verification successful
Verified compatibility with Go 1.22.
The project is using Go version 1.22.2, which is compatible with the updated dependency
github.com/mgechev/reviveversion 1.3.9. No issues found.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify that the project is compatible with Go 1.22. # Test: Check the Go version used in the project. grep -r "go 1.22" go.modLength of output: 36
213-213: Verify compatibility withgolang.org/x/termv0.22.0.Ensure that the update from
v0.20.0tov0.22.0does not introduce any breaking changes and aligns with the project's requirements.
212-212: Verify compatibility withgolang.org/x/sysv0.22.0.Ensure that the update from
v0.20.0tov0.22.0does not introduce any breaking changes and aligns with the project's requirements.
207-207: Verify compatibility withgolang.org/x/cryptov0.25.0.Ensure that the update from
v0.23.0tov0.25.0does not introduce any breaking changes and aligns with the project's requirements.
208-208: Verify compatibility withgolang.org/x/modv0.19.0.Ensure that the update from
v0.14.0tov0.19.0does not introduce any breaking changes and aligns with the project's requirements.
98-98: Verify compatibility withgithub.com/fatih/colorv1.17.0.Ensure that the update from
v1.16.0tov1.17.0does not introduce any breaking changes and aligns with the project's requirements.
54-54: Verify compatibility withgithub.com/BurntSushi/tomlv1.4.0.Ensure that the update from
v1.3.2tov1.4.0does not introduce any breaking changes and aligns with the project's requirements.
209-209: Verify compatibility withgolang.org/x/netv0.27.0.Ensure that the update from
v0.25.0tov0.27.0does not introduce any breaking changes and aligns with the project's requirements.Verification successful
Verified compatibility with
golang.org/x/netv0.27.0.The update from
v0.25.0tov0.27.0does not introduce any breaking changes. The package is listed as an indirect dependency, and no direct imports were found in the project's codebase.
go.mod:golang.org/x/net v0.27.0 // indirectgo.sum: Multiple entries forgolang.org/x/netScripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify compatibility with `golang.org/x/net` v0.27.0. # Test: Check for usage of `golang.org/x/net` in the project. rg --type go "golang.org/x/net"Length of output: 31
Script:
#!/bin/bash # Description: Verify indirect usage of `golang.org/x/net` in the project. # Test: Check for `golang.org/x/net` in go.mod and go.sum files. rg "golang.org/x/net" go.mod go.sum # Test: Check for import statements in Go files that might indirectly reference `golang.org/x/net`. rg --type go "import .*golang.org/x/net"Length of output: 7102
214-214: Verify compatibility withgolang.org/x/textv0.16.0.Ensure that the update from
v0.15.0tov0.16.0does not introduce any breaking changes and aligns with the project's requirements.Verification successful
Verify compatibility with
golang.org/x/textv0.16.0.The dependency
golang.org/x/textis listed as an indirect dependency and no direct usage was found in the codebase. The update fromv0.15.0tov0.16.0should not directly affect the project. However, it is recommended to run the project's tests to ensure there are no issues.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify compatibility with `golang.org/x/text` v0.16.0. # Test: Check for usage of `golang.org/x/text` in the project. rg --type go "golang.org/x/text"Length of output: 32
Script:
#!/bin/bash # Description: Verify compatibility with `golang.org/x/text` v0.16.0. # Test 1: Check for any references to `golang.org/x/text` in all Go files. rg "golang.org/x/text" --type go -A 5 # Test 2: Check the `go.mod` file for any related dependencies or changes. cat go.mod # Test 3: Check the `go.sum` file for any related dependencies or changes. cat go.sumLength of output: 178246
216-216: Verify compatibility withgolang.org/x/toolsv0.23.0.Ensure that the update from
v0.17.0tov0.23.0does not introduce any breaking changes and aligns with the project's requirements.Verification successful
The
golang.org/x/toolsdependency is an indirect dependency and does not appear to be actively used in the codebase. No further action is required.
- The dependency is listed in
go.modandgo.sumfiles but not referenced in the source files.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify compatibility with `golang.org/x/tools` v0.23.0. # Test: Check for usage of `golang.org/x/tools` in the project. rg --type go "golang.org/x/tools"Length of output: 33
Script:
#!/bin/bash # Description: Verify compatibility with `golang.org/x/tools` v0.23.0. # Test 1: Check for usage of `golang.org/x/tools` in the go.sum file. rg "golang.org/x/tools" go.sum # Test 2: Perform a comprehensive search for `golang.org/x/tools` references in the codebase. rg "golang.org/x/tools" --type goLength of output: 6211
Script:
#!/bin/bash # Description: Verify compatibility with `golang.org/x/tools` v0.23.0. # Test: Search for common packages that might use `golang.org/x/tools` indirectly. rg "golang.org/x/tools" --type go # Check for common packages that depend on `golang.org/x/tools`. rg "golang.org/x/lint" --type go rg "golang.org/x/tools/go" --type go rg "golang.org/x/tools/cmd" --type goLength of output: 141
Script:
#!/bin/bash # Description: Verify compatibility with `golang.org/x/tools` v0.23.0. # List all dependencies in the go.mod file. cat go.mod # Check for any dependencies that might depend on `golang.org/x/tools`. rg "require" go.mod | grep -E "golang.org/x/tools|golang.org/x/lint|golang.org/x/tools/go|golang.org/x/tools/cmd"Length of output: 11738
134-134: Verify compatibility withgithub.com/hashicorp/go-versionv1.7.0.Ensure that the update from
v1.6.0tov1.7.0does not introduce any breaking changes and aligns with the project's requirements.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2576 +/- ##
===========================================
- Coverage 75.38% 62.55% -12.84%
===========================================
Files 100 275 +175
Lines 8025 16035 +8010
===========================================
+ Hits 6050 10031 +3981
- Misses 1589 5231 +3642
- Partials 386 773 +387 |
There was a problem hiding this comment.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files ignored due to path filters (1)
go.sumis excluded by!**/*.sum
Files selected for processing (1)
- go.mod (5 hunks)
Additional comments not posted (11)
go.mod (11)
24-24: LGTM! Verify compatibility with Go 1.22.The update to
github.com/mgechev/revivefrom version1.3.7to1.3.9is approved. Ensure compatibility with Go 1.22, as support for Go 1.20 has been dropped.Verification successful
Compatibility with Go 1.22 verified for
github.com/mgechev/reviveupdateThe update to
github.com/mgechev/revivefrom version1.3.7to1.3.9does not introduce any compatibility issues with Go 1.22, as its usage is limited to linting configurations. No deprecated features or APIs are in use.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify compatibility of `github.com/mgechev/revive` with Go 1.22. # Test: Check for any usage of deprecated features or APIs in the codebase. rg --type go 'revive' -A 5Length of output: 862
207-207: LGTM! Verify for breaking changes.The update to
golang.org/x/modfrom version0.14.0to0.19.0is approved. Check for any breaking changes in the updated version.
54-54: LGTM! Verify for breaking changes.The update to
github.com/BurntSushi/tomlfrom version1.3.2to1.4.0is approved. Check for any breaking changes in the updated version.Verification successful
No breaking changes found for
github.com/BurntSushi/tomlupdate.The search did not reveal any direct usage of the
github.com/BurntSushi/tomlpackage in the codebase. Therefore, the update to version1.4.0should not introduce any breaking changes.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify for breaking changes in `github.com/BurntSushi/toml` update. # Test: Search for any deprecated or changed APIs in the codebase. rg --type go 'toml' -A 5Length of output: 4668
134-134: LGTM! Verify for breaking changes.The update to
github.com/hashicorp/go-versionfrom version1.6.0to1.7.0is approved. Check for any breaking changes in the updated version.Verification successful
No breaking changes detected for
github.com/hashicorp/go-versionupdate.The update to
github.com/hashicorp/go-versionfrom version1.6.0to1.7.0does not appear to introduce any breaking changes, as there is no direct usage of the package in the codebase. The update is safe to proceed.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify for breaking changes in `github.com/hashicorp/go-version` update. # Test: Search for any deprecated or changed APIs in the codebase. rg --type go 'go-version' -A 5Length of output: 30
Script:
#!/bin/bash # Description: Verify for breaking changes by searching for import statements and function calls related to `github.com/hashicorp/go-version`. # Search for import statements of `github.com/hashicorp/go-version`. rg --type go 'import.*"github.com/hashicorp/go-version"' -A 5 # Search for function calls from the `go-version` package. rg --type go 'version\.' -A 5Length of output: 679
212-212: LGTM! Verify for breaking changes.The update to
golang.org/x/termfrom version0.20.0to0.22.0is approved. Ensure there are no breaking changes in the updated version.Verification successful
No direct usage of
golang.org/x/termfound.The
golang.org/x/termpackage is not directly imported in the codebase, indicating that it is likely a transitive dependency. As such, the update to version0.22.0should not introduce direct breaking changes to the codebase.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify for breaking changes in `golang.org/x/term` update. # Test: Search for any deprecated or changed APIs in the codebase. rg --type go 'x/term' -A 5Length of output: 26
Script:
#!/bin/bash # Description: Check for any direct or indirect usage of `golang.org/x/term` in the codebase. # Search for any import statements or references to `golang.org/x/term`. rg 'import.*"golang.org/x/term"' --type go -A 3Length of output: 49
211-211: LGTM! Verify for breaking changes.The update to
golang.org/x/sysfrom version0.20.0to0.22.0is approved. Ensure there are no breaking changes in the updated version.
208-208: LGTM! Verify for breaking changes.The update to
golang.org/x/netfrom version0.25.0to0.27.0is approved. Ensure there are no breaking changes in the updated version.
215-215: LGTM! Verify for breaking changes.The update to
golang.org/x/toolsfrom version0.17.0to0.23.0is approved. Ensure there are no breaking changes in the updated version.
206-206: LGTM! Verify for breaking changes.The update to
golang.org/x/cryptofrom version0.23.0to0.25.0is approved. Ensure there are no breaking changes in the updated version.Verification successful
No direct impact from
golang.org/x/cryptoupdate.The update to
golang.org/x/cryptofrom version0.23.0to0.25.0does not directly impact the codebase as there are no direct imports found. It is marked as anindirectdependency, suggesting it is used by other packages. Ensure to verify with maintainers of any packages that might rely on this dependency for potential indirect impacts.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify for breaking changes in `golang.org/x/crypto` update. # Test: Search for any deprecated or changed APIs in the codebase. rg --type go 'x/crypto' -A 5Length of output: 28
Script:
#!/bin/bash # Description: Check for direct imports of `golang.org/x/crypto` in the codebase. # Search for files importing `golang.org/x/crypto` rg 'import\s+"golang.org/x/crypto' --type goLength of output: 46
98-98: LGTM! Verify for breaking changes.The update to
github.com/fatih/colorfrom version1.16.0to1.17.0is approved. Ensure there are no breaking changes in the updated version.Verification successful
No direct usage of
github.com/fatih/colorfound in the codebase.The package is listed as an indirect dependency, and there are no indications of breaking changes affecting the current code. The update to version
v1.17.0should not impact the codebase directly.
go.modlistsgithub.com/fatih/coloras an indirect dependency.go.sumincludes checksums for versionv1.17.0.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify for breaking changes in `github.com/fatih/color` update. # Test: Search for any deprecated or changed APIs in the codebase. rg --type go 'color' -A 5Length of output: 2928
Script:
#!/bin/bash # Description: Search for direct usage of `github.com/fatih/color` in the codebase. # Test: Search for any usage of the `github.com/fatih/color` package. rg --type go 'github.com/fatih/color' -A 5Length of output: 42
Script:
#!/bin/bash # Description: Search for references to `github.com/fatih/color` in build or dependency management files. # Test: Search for any references to the `github.com/fatih/color` package in go.mod or go.sum files. rg 'github.com/fatih/color' go.mod go.sumLength of output: 363
213-213: LGTM! Verify for breaking changes.The update to
golang.org/x/textfrom version0.15.0to0.16.0is approved. Ensure there are no breaking changes in the updated version.
gsk967
deleted the
dependabot/go_modules/github.com/mgechev/revive-1.3.9
branch
Bumps github.com/mgechev/revive from 1.3.7 to 1.3.9.
Release notes
Sourced from github.com/mgechev/revive's releases.
Commits
9ec5e55Update goreleaser version to 1.22 (#1016)0eb2e24Drop go 1.20, add go 1.22 in GH actions (#1015)bedce65Fix goreleaser (#1014)7ef710afix(1007): return Sel.Name as FuncName when selector is an CallExpr (#1012)a2174a3fix(deps): update module golang.org/x/tools to v0.23.0 (#1006)bf7adb6Update README.md & Typo (#1010)689291frule optimize-operands-order: do not consider built-in len as a caller (#1005)0df1bb0Fix a performance regression #995 (#998)9c2d25cdocs: clean (#996)8fe6c06fix(deps): update module golang.org/x/tools to v0.22.0 (#999)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)Summary by CodeRabbit