Skip to content

chore(deps): update dependency vektra/mockery to v3.7.2 - #46

Open
scality-renovate[bot] wants to merge 1 commit into
mainfrom
renovate/vektra-mockery-3.x
Open

chore(deps): update dependency vektra/mockery to v3.7.2#46
scality-renovate[bot] wants to merge 1 commit into
mainfrom
renovate/vektra-mockery-3.x

Conversation

@scality-renovate

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
vektra/mockery patch v3.7.1v3.7.2
vektra/mockery patch 3.7.13.7.2

Release Notes

vektra/mockery (vektra/mockery)

v3.7.2

Compare Source

What's Changed

New Contributors

Full Changelog: vektra/mockery@v3.7.1...v3.7.2


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "before 9am on monday"
  • 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 these updates again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate.

@github-actions

github-actions Bot commented Aug 3, 2026

Copy link
Copy Markdown

Dependency Bump Evaluation

Version change: v3.7.1 → v3.7.2 (patch)
Semver bump type: patch

Changes:

  • FAQ: highlight that package path errors can be due to case mismatch (docs only)
  • Fix typos in comments and docs (docs only)
  • Match interface{} as well as any in mock generation (compatibility fix)

Breaking changes: None

Security concerns: None — mockery is a dev-only code generation tool, not a runtime dependency

Impact on codebase: No impact. The codebase uses any exclusively (0 occurrences of interface{}), so the interface{} matching fix is irrelevant. The diff only bumps version pins in .devcontainer/Dockerfile and .github/workflows/pre-merge.yaml.

Recommendation: SAFE TO MERGE

Notes: CI checks (build, lint, generate, test) are still in progress at time of evaluation. Verify they pass before merging. The generate check will confirm the updated mockery produces identical mocks.

— Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants