Skip to content
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

Bump cabal-version #10896

Merged
merged 1 commit into from
Apr 5, 2025
Merged

Bump cabal-version #10896

merged 1 commit into from
Apr 5, 2025

Conversation

ffaf1
Copy link
Collaborator

@ffaf1 ffaf1 commented Apr 2, 2025

3.0 uses SPDX License List version 3.6 2019-07-10
3.4 uses SPDX License List version 3.9 2020-05-15

cabal-version 3.0 is out of our support window.


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).

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.

Thank you.

@Mikolaj
Copy link
Member

Mikolaj commented Apr 2, 2025

BTW, how about doing this also in Cabal-syntax, as mentioned in the release checklist?

@ffaf1 ffaf1 force-pushed the bump-cabal-version branch 2 times, most recently from f72bf87 to aafad59 Compare April 2, 2025 11:20
@ffaf1
Copy link
Collaborator Author

ffaf1 commented Apr 2, 2025

I have bumped all the things

@Mikolaj Mikolaj added the merge me Tell Mergify Bot to merge label Apr 3, 2025
@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 Apr 5, 2025
Copy link
Contributor

mergify bot commented Apr 5, 2025

This pull request has been removed from the queue for the following reason: pull request branch update failed.

The pull request can't be updated

You should update or rebase your pull request manually. If you do, this pull request will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

For `Cabal`, `Cabal-syntax`, `Cabal-hooks`, `cabal-install, and
`cabal-install-solver`.

Our support window for `cabal-version` is five years.
3.0 uses SPDX License List version 3.6 2019-07-10
3.4 uses SPDX License List version 3.9 2020-05-15
@ffaf1 ffaf1 force-pushed the bump-cabal-version branch from aafad59 to c0cbee3 Compare April 5, 2025 20:37
@mergify mergify bot merged commit 9d4b21a into haskell:master Apr 5, 2025
52 checks passed
@ffaf1 ffaf1 deleted the bump-cabal-version branch April 6, 2025 06:23
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 ready and waiting Mergify is waiting out the cooldown period
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants