-
Notifications
You must be signed in to change notification settings - Fork 33
Bump mock from 4.0.3 to 5.2.0 #114
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
Conversation
@dependabot rebase |
1 similar comment
@dependabot rebase |
ec7fa97
to
198e1e5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR bumps the dependency for the mock library from version 4.0.3 to allow versions up to but not including 6.0.0, preparing for compatibility with the latest release (5.2.0).
- Updated dependency version constraint for mock in pyproject.toml
- Sets an upper limit (<6.0.0) to guard against unexpected major version changes
Comments suppressed due to low confidence (1)
pyproject.toml:29
- The updated dependency version constraint appropriately limits changes to the mock package. Please verify that our tests cover all relevant functionality affected by potential 5.x release updates.
mock = ">=4.0.3,<6.0.0"
198e1e5
to
138035d
Compare
@dependabot rebase |
Bumps [mock](https://github.com/testing-cabal/mock) from 4.0.3 to 5.2.0. - [Changelog](https://github.com/testing-cabal/mock/blob/master/CHANGELOG.rst) - [Commits](testing-cabal/mock@4.0.3...5.2.0) --- updated-dependencies: - dependency-name: mock dependency-version: 5.2.0 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
138035d
to
72e5378
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR updates the version constraint for the mock
dependency to allow any 5.x
release while capping at <6.0.0
.
- Changed
mock
requirement inpyproject.toml
from a caret-pinned^4.0.3
to a range allowing up to but not including6.0.0
.
urllib3 = "^1.26.12" | ||
flake8 = "^5" | ||
mock = "^4.0.3" | ||
mock = ">=4.0.3,<6.0.0" |
Copilot
AI
Jun 3, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The lower bound remains at 4.0.3, so projects may still install earlier 4.x versions. To ensure users get the new 5.2.0 release, bump the lower bound to >=5.2.0,<6.0.0
.
mock = ">=4.0.3,<6.0.0" | |
mock = ">=5.2.0,<6.0.0" |
Copilot uses AI. Check for mistakes.
Bumps mock from 4.0.3 to 5.2.0.
Changelog
Sourced from mock's changelog.
... (truncated)
Commits
0f5df82
In memoriam: Michael Foord 1974-20253c737e2
Preparing for 5.2.0 release.563f311
latest sync point4fc238e
unittest.mock
test and coverage fixup (#130787)aee44ed
Backport-specific code coverage fixes9081bbe
Fix bug in backporting docsfdacaa2
Add set_event_loop_policy to backports4221c21
Revert "gh-71339: Add additional assertion methods for unittest (GH-128707)"45d2d49
gh-71339: Add additional assertion methods for unittest (GH-128707)9e3f49c
gh-127949: deprecateasyncio.set_event_loop_policy
(#128024)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)