Skip to content

cabal-install-3.12: allow open-browser-0.4 #11085

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

Open
wants to merge 1 commit into
base: 3.12
Choose a base branch
from
Open

cabal-install-3.12: allow open-browser-0.4 #11085

wants to merge 1 commit into from

Conversation

juhp
Copy link
Collaborator

@juhp juhp commented Jul 21, 2025

No description provided.

@juhp
Copy link
Collaborator Author

juhp commented Jul 21, 2025

I successfully built locally with stack --resolver lts-24 --allow-newer build cabal-install-3.12.1.0

@geekosaur
Copy link
Collaborator

Wait, 3.12? Metadata revisions are fine but I don't think we're making any more releases on this branch.

@ulysses4ever
Copy link
Collaborator

I don't think we are either. I think downstream distributors just want to have the branch closer to what they need to build it successfully. @juhp could you clarify this maybe? (Sorry if you did this before but I don't know if a past discussion like that has reached the right audience).

@juhp
Copy link
Collaborator Author

juhp commented Jul 22, 2025

I am really just looking for a revision so we can have cabal-install in lts-24 (I wish this happened "automatically")

@geekosaur
Copy link
Collaborator

Okay. I think we're go on the revision, since Linux and most MacOS jobs succeeded; both sets of failures appear to be GitHub issues (currently all our Windows jobs are failing the same way).

@geekosaur
Copy link
Collaborator

I've updated the metadata for 3.12.1.0, and cabal update should get it soonish (depending on how long CloudFlare needs to refresh).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants