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

Update Mockery to 1.6.4 #228

Merged
merged 2 commits into from
Jul 21, 2023
Merged

Update Mockery to 1.6.4 #228

merged 2 commits into from
Jul 21, 2023

Conversation

unfulvio-godaddy
Copy link
Member

@unfulvio-godaddy unfulvio-godaddy commented Jul 20, 2023

Summary

This PR updates Mockery to 1.6.4 (from 1.6.2).

Changelog: https://github.com/mockery/mockery/releases/tag/1.6.4
Diff: mockery/mockery@1.6.2...1.6.4

I have run the following:

 composer update phpunit/phpunit mockery/mockery antecedente/patchwork

Details

Contributor checklist

  • I agree to follow this project's Code of Conduct.
  • I have updated the documentation accordingly
  • I have added tests to cover changes introduced by this pull request
  • All new and existing tests pass

Testing

Reviewer checklist

  • Code changes review
  • Documentation changes review
  • Unit tests pass
  • Static analysis passes

@unfulvio-godaddy unfulvio-godaddy added this to the v1.0.0 milestone Jul 20, 2023
@coveralls
Copy link

coveralls commented Jul 20, 2023

Coverage Status

coverage: 65.513%. remained the same when pulling e959863 on chore/update-dependencies into 0ca2039 on trunk.

@unfulvio-godaddy unfulvio-godaddy self-assigned this Jul 20, 2023
@unfulvio-godaddy unfulvio-godaddy requested a review from a team July 20, 2023 05:13
@@ -177,37 +177,33 @@
},
{
"name": "mockery/mockery",
"version": "1.6.2",
"version": "1.6.4",
Copy link
Contributor

Choose a reason for hiding this comment

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

I think projects using wp_mock can still install older versions of Mockery, as long as they match the "mockery/mockery": "^1.6", restriction. Not a bad thing in this case, but I wanted to point that out.

I don't know when is the right time to bump minimum requirements in a public repo like this one. Perhaps we need a specific reason for doing so.

In our private packages, we could depend on mockery directly too, to set the minimums that we want.

Copy link
Contributor

@wvega-godaddy wvega-godaddy left a comment

Choose a reason for hiding this comment

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

LGTM!

@wvega-godaddy wvega-godaddy merged commit e7470ed into trunk Jul 21, 2023
@wvega-godaddy wvega-godaddy deleted the chore/update-dependencies branch July 21, 2023 19:31
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.

3 participants