-
Notifications
You must be signed in to change notification settings - Fork 701
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
final fixups to sdist check #10478
final fixups to sdist check #10478
Conversation
e2c1861
to
6555721
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.
Looks plausible...
It led to the first actual success of the check on 3.12 branch where it originated (as a fixup to #10477), so I'm fairly confident that it's now working properly. |
3805ba4
to
1870676
Compare
Not needed for 3.14 release, but we probably want it in the tree before we make any later 3.14 releases so we can verify that they don't break compatibility with the bundled Cabal in 9.12.1. Note that the backport will need |
@geekosaur I believe this can go in. I'll start the process of producing the binaries after it's merged. |
There's no reason it can't, it just won't do anything until post-release and even then it'll only affect CI, so I don't see much point to it slowing the release. |
validated on 3.12 branch and applied in backport of haskell#10448; this brings the fixes up to `master`
1870676
to
8e076b6
Compare
@mergify backport 3.14 |
✅ Backports have been created
|
Backport #10478: final fixups to sdist check
@mergify backport 3.14.1.1 |
✅ Backports have been created
|
turns out we need it because I added the branch protection rule… after the release. which wouldn't have been a problem except for this emergency release. |
validated on 3.12 branch and applied in backport of #10448; this brings the fixes up to
master
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:
Is this a PR that fixes CI? If so, it will need to be backported to older cabal release branches (ask maintainers for directions).actually taken from a backport!