Skip to content

Preflight checks for 3.16 #11011

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

Merged
merged 2 commits into from
Jun 23, 2025
Merged

Preflight checks for 3.16 #11011

merged 2 commits into from
Jun 23, 2025

Conversation

ffaf1
Copy link
Collaborator

@ffaf1 ffaf1 commented Jun 23, 2025

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:

  • Patches conform to the coding conventions.
  • Is this a PR that fixes CI? If so, it will need to be backported to older cabal release branches (ask maintainers for directions). N/A

Our support window for `cabal-version` is five years.
@ulysses4ever ulysses4ever requested a review from Mikolaj June 23, 2025 17:44
Copy link
Member

@Mikolaj Mikolaj left a comment

Choose a reason for hiding this comment

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

@mergify mergify bot added merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days ready and waiting Mergify is waiting out the cooldown period labels Jun 23, 2025
@ulysses4ever
Copy link
Collaborator

I took the liberty to set the label

@mergify mergify bot merged commit f5453c7 into haskell:master Jun 23, 2025
54 checks passed
@ffaf1 ffaf1 deleted the preflight-3.16 branch June 24, 2025 05:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days merge me Tell Mergify Bot to merge priority: high 🔥 ready and waiting Mergify is waiting out the cooldown period release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants