-
Notifications
You must be signed in to change notification settings - Fork 696
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
Skip tasty-quickcheck 0.11 #10136
Skip tasty-quickcheck 0.11 #10136
Conversation
Sorting out where it needs to be changed. |
a5563cd
to
22246f4
Compare
22246f4
to
4b07f2d
Compare
I think that, since this may delay the release if we need to make fixes after the candidate goes up, we should skip the delay on this one. |
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.
Why is the change for Mergify config a part of this PR?
agree on skipping the delay btw |
Ugh, I thought I switched to |
4b07f2d
to
2cb6ea5
Compare
Reverted |
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.
Thanks!
Hm, commits still show as present, although a squash will fix that. Dunno if it's worth mangling the repo to fix. |
API incompatible with our test suites
2cb6ea5
to
3964da3
Compare
Okay, history is clean now. |
Cheers @geekosaur |
@mergify backport 3.12 |
✅ Backports have been created
|
Skip tasty-quickcheck 0.11 (backport #10136)
tasty-quickcheck 0.11, which was just released, is API incompatible with earlier versions. Exclude it from build plans. (Why were we using it without an upper bound?)
Template B: This PR does not modify behaviour or interface
E.g. the PR only touches documentation or tests, does refactorings, etc.
Include the following checklist in your PR: