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

chore(deps): update golangci/golangci-lint-action action to v6 #454

Merged
merged 1 commit into from
May 29, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 7, 2024

Mend Renovate

This PR contains the following updates:

Package Type Update Change
golangci/golangci-lint-action action major v4.0.1 -> v6.0.1

Release Notes

golangci/golangci-lint-action (golangci/golangci-lint-action)

v6.0.1

Compare Source

What's Changed

Changes

Full Changelog: golangci/golangci-lint-action@v6.0.0...v6.0.1

v6.0.0

Compare Source

What's Changed

This version removes annotations option (because it was useless), and removes the default output format (github-actions).
The annotations are still produced but with another approach.

Changes
Dependencies

Full Changelog: golangci/golangci-lint-action@v5.3.0...v6.0.0

v5.3.0

Compare Source

What's Changed

Changes

Full Changelog: golangci/golangci-lint-action@v5.2.0...v5.3.0

v5.2.0

Compare Source

What's Changed

Changes

Full Changelog: golangci/golangci-lint-action@v5.1.0...v5.2.0

v5.1.0

Compare Source

What's Changed

Changes
Dependencies

Full Changelog: golangci/golangci-lint-action@v5.0.0...v5.1.0

v5.0.0

Compare Source

What's Changed

skip-pkg-cache and skip-build-cache have been removed because the cache related to Go itself is already handled by actions/setup-go.

Changes

New Contributors

Full Changelog: golangci/golangci-lint-action@v4.0.1...v5.0.0


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/golangci-golangci-lint-action-6.x branch from 8dd3b59 to 27dd82f Compare May 8, 2024 05:15
@renovate renovate bot force-pushed the renovate/golangci-golangci-lint-action-6.x branch 2 times, most recently from d99fa1d to 4780622 Compare May 29, 2024 00:24
Copy link

codecov bot commented May 29, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.62%. Comparing base (5bb7441) to head (8b14a42).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #454   +/-   ##
=======================================
  Coverage   86.62%   86.62%           
=======================================
  Files          11       11           
  Lines        1712     1712           
=======================================
  Hits         1483     1483           
  Misses        155      155           
  Partials       74       74           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@fclairamb fclairamb enabled auto-merge (squash) May 29, 2024 00:31
@renovate renovate bot force-pushed the renovate/golangci-golangci-lint-action-6.x branch 2 times, most recently from c6349b5 to 13e6ca9 Compare May 29, 2024 07:48
@renovate renovate bot force-pushed the renovate/golangci-golangci-lint-action-6.x branch from 13e6ca9 to 8b14a42 Compare May 29, 2024 10:58
@fclairamb fclairamb merged commit 1586bde into main May 29, 2024
5 checks passed
@fclairamb fclairamb deleted the renovate/golangci-golangci-lint-action-6.x branch May 29, 2024 11:00
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

1 participant