-
Notifications
You must be signed in to change notification settings - Fork 697
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
check
: add PackageInfo warning
#9525
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ffaf1
changed the title
Dec 15, 2023
check
: guard PackageInfo behind cabal-version ≥ 3.12check
: add PackageInfo warning
ffaf1
force-pushed
the
autogen-check-3.10
branch
2 times, most recently
from
December 15, 2023 19:06
2a5bacf
to
b6f775d
Compare
Mikolaj
approved these changes
Dec 16, 2023
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.
Spot on.
ffaf1
added
squash+merge me
Tell Mergify Bot to squash-merge
and removed
attention: needs-review
cabal-install: cmd/check
labels
Dec 16, 2023
Mikolaj
added
merge me
Tell Mergify Bot to merge
and removed
squash+merge me
Tell Mergify Bot to squash-merge
merge me
Tell Mergify Bot to merge
labels
Dec 21, 2023
@mergify squash |
Add test for haskell#9331 Guard Paths_* behind `cabal-version: 3.12` or higher, “fail” and “succeed” tests. * check: guard PackageInfo behind cabal-version ≥ 3.12 Note we do not actually check for ≥ 3.12, since it is not possible to introduce constructors in point release. Instead the check always fires with PackageInfo_* is present, and suggests an upgrade path. * Fix testsuite * Add changelog
✅ Pull request squashed successfully |
Mikolaj
force-pushed
the
autogen-check-3.10
branch
from
December 21, 2023 18:07
b6f775d
to
90249c6
Compare
Mikolaj
added
the
merge delay passed
Applied (usually by Mergify) when PR approved and received no updates for 2 days
label
Dec 21, 2023
That's not a real backport, but an original PR, which is probably why mergify ignores us. Given that, I'm going to merge via the big red button. |
@mergify rebase |
✅ Nothing to do for rebase action |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
backport
merge delay passed
Applied (usually by Mergify) when PR approved and received no updates for 2 days
merge me
Tell Mergify Bot to merge
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
“Backport” of #9481, should be the last step (and close) #9331.
Include the following checklist in your PR:
QA instructions
cabal check
will warn and suggest you to update tocabal
3.12.Things to double-check:
PackageInfo_*
module, regardless ofcabal-version
)cabal-version
. #9331?