chore(deps): update dependency nunnatsa/ginkgolinter to v0.21.2 #67
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
This PR contains the following updates:
0.19.1->0.21.2Release Notes
nunnatsa/ginkgolinter (nunnatsa/ginkgolinter)
v0.21.2Compare Source
What's Changed
Full Changelog: nunnatsa/ginkgolinter@v0.21.0...v0.21.2
v0.21.1Compare Source
v0.21.0Compare Source
What's Changed
Added new linter rule.
Bump golang to 1.24
New Linter Rule
Force NotTo() [STYLE] (#208)
This rule enforces using the
NotTo()orShouldNot()assertion methods instead ofTo(Not())or
Should(Not()).This rule is disabled by default. Use the
--force-tonotcommand line flag to enable it.CLI Changes
Added the new
--force-tonot=truecommand line parameter, to enable the "Force NotTo()" rule.New Contributors
Full Changelog: nunnatsa/ginkgolinter@v0.20.0...v0.21.0
v0.20.0Compare Source
What's Changed
Added new linter rule.
New Linter Rule
Force assertion descriptions [STYLE] (#200)
Note: This rule does not support auto-fix.
Correct Usage of the Succeed() and the
HaveOccurred()matchers [STYLE]This rule enforces that all assertions include an optional description message to improve test readability and debugging.
Should be:
This rule is disabled by default. Use the
--force-assertion-descriptioncommand line flag to enable it.Note: This rule does not support auto-fix.
CLI Changes
Added the new
--force-assertion-description=truecommand line parameter, to enable the "Force assertion descriptions" rule.New Contributors
Full Changelog: nunnatsa/ginkgolinter@v0.19.1...v0.20.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.
This PR was generated by Mend Renovate. View the repository job log.