-
Notifications
You must be signed in to change notification settings - Fork 842
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
Cut a new release version - (v1.6.6 or v1.7) #3954
Comments
We're hoping to release 1.7 soon, so I've asked @mgsloan about the priotiy on those issues. The Cabal-2.2 changes are too big to backport to 1.6, so it'll have to be a new major release. |
I'm glad to hear the new release is coming soon. Is there a time table for the |
@dukedave I think so! I'm sure there's a bit a of a review process in tagging a new release, something I'm unfamiliar with. I'm hoping the Stack team can make progress on that next week! |
Release candidate for v1.7.1: https://github.com/commercialhaskell/stack/releases/tag/v1.7.0.1 |
@borsboom I tried to build this minimum working example test repository that requires the I ran the following commands:
I got the following output:
There were a lot of warnings emitted regarding the |
That's because GHC 8.2.2 comes with Cabal-2.0.1.0 and so that is the version that's used to build your package. Change the resolver in |
@borsboom thanks for the technical assistance, let me try to rebuild in the morning with I did try bumping the |
@borsboom the test repository does build with the v1.7.0.1 release candidate after ensuring that the resolver used |
I've been waiting to use features added to
Cabal-2.2.*
in conjunction withstack
for a month now. Unfortunately there's been no traction on the three issues listed as blocking release (#3796, #3791, #3782).Specifically I need to use the
cxx-options
andcxx-sources
buildinfo fields for separate compilation of C and C++ source files.stack
's lack of support of these features is roadblocking our development and continuous integration efforts.Could you prioritize resolving issues blocking a release incorporating
Cabal-2.2.*
?The text was updated successfully, but these errors were encountered: