Skip to content
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

fix(deps): Update dependency golangci/golangci-lint to v1.49.0 #1553

Closed
wants to merge 1 commit into from

Conversation

cq-bot
Copy link
Contributor

@cq-bot cq-bot commented Aug 25, 2022

This PR contains the following updates:

Package Update Change
golangci/golangci-lint minor v1.47.3 -> v1.49.0

Release Notes

golangci/golangci-lint

v1.49.0

Compare Source

IMPORTANT: varcheck and deadcode has been removed of default linters.

  1. new linters
  2. updated linters
    • go-colorable: from 0.1.12 to 0.1.13
    • go-critic: from 0.6.3 to 0.6.4
    • go-errorlint: from 1.0.0 to 1.0.2
    • go-exhaustruct: from 2.2.2 to 2.3.0
    • gopsutil: from 3.22.6 to 3.22.7
    • gosec: from 2.12.0 to 2.13.1
    • revive: from 1.2.1 to 1.2.3
    • usestdlibvars: from 1.8.0 to 1.13.0
    • contextcheck: from v1.0.4 to v1.0.6 && re-enable
    • nosnakecase: This linter is deprecated.
    • varcheck: This linter is deprecated use unused instead.
    • deadcode: This linter is deprecated use unused instead.
    • structcheck: This linter is deprecated use unused instead.
  3. documentation
    • revive: fix wrong URL
    • Add a section about default exclusions
    • usestdlibvars: fix typo in documentation
    • nolintlint: remove allow-leading-space option
    • Update documentation and assets
  4. misc.
    • dev: rewrite the internal tests framework
    • fix: exit early on run --version
    • fix: set an explicit GOROOT in the Docker image for go-critic

v1.48.0

Compare Source

  1. new linters
  2. updated linters
    • contextcheck: disable linter
    • errcheck: from 1.6.1 to 1.6.2
    • gci: add missing custom-order setting
    • gci: from 0.5.0 to 0.6.0
    • ifshort: deprecate linter
    • nolint: drop allow-leading-space option and add "nolint:all"
    • revgrep: bump to HEAD
  3. documentation
    • remove outdated info on source install
  4. misc
    • go1.19 support

Configuration

📅 Schedule: Branch creation - "before 3am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

@github-actions github-actions bot added the fix label Aug 25, 2022
Copy link
Contributor

@erezrokah erezrokah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't merge yet as the lint run was skipped

@github-actions github-actions bot added fix and removed fix labels Aug 25, 2022
@cq-bot cq-bot force-pushed the renovate/golangci-golangci-lint-1.x branch from 30b53da to c54bf0c Compare August 25, 2022 07:51
@github-actions github-actions bot added fix and removed fix labels Aug 25, 2022
@erezrokah
Copy link
Contributor

This update is blocked by golangci/golangci-lint-action#535. We could also update to go@1.19 to fix it, but out of scope for this PR

@erezrokah erezrokah closed this Aug 25, 2022
@erezrokah erezrokah deleted the renovate/golangci-golangci-lint-1.x branch August 25, 2022 07:58
@cq-bot
Copy link
Contributor Author

cq-bot commented Aug 25, 2022

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will now ignore this update (v1.49.0). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the ignoreDeps array of your renovate config.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants