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

Allow newer hspec, free #1690

Merged
merged 1 commit into from
Jun 26, 2023
Merged

Allow newer hspec, free #1690

merged 1 commit into from
Jun 26, 2023

Conversation

ysangkok
Copy link
Contributor

@ysangkok ysangkok commented Jun 26, 2023

Especially the free bound is important for inclusion into Stackage Nightly.

I have also bumped the min bound for servant-auth, since jose-0.10 requires aeson-2, we might as well.

Also included is a bump for monad-time.

@ysangkok ysangkok merged commit 5da422b into master Jun 26, 2023
16 checks passed
@ysangkok ysangkok deleted the janus/allow-hspec-free branch June 26, 2023 10:37
@ysangkok
Copy link
Contributor Author

@maksbotan Would it be possible for you to revise servant-client-core-0.20's upper free bound? Then we could get the client back into Nightly.

@maksbotan
Copy link
Contributor

@ysangkok sure, done!

do other packages have to be revised as well?

@ysangkok
Copy link
Contributor Author

ysangkok commented Jun 26, 2023

Thank you!

It's not strictly necessary to bump all packages, as hspec is only for running tests. But if you like, you can bump all these hspec bounds, and then Nightly users will be able to run the test suites.

@maksbotan
Copy link
Contributor

afair, stackage runs tests when building lts, so I will make those revisions. later this day

wonder if that can be automated 🤔

@@ -35,7 +35,7 @@ library
build-depends:
base >= 4.10 && < 4.19
, containers >= 0.6 && < 0.7
, aeson >= 1.3.1.1 && < 3
, aeson >= 2.0 && < 3
Copy link
Contributor

Choose a reason for hiding this comment

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

@ysangkok is this really necessary?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

the version of jose we use doesn't permit aeson 1.x. So I think it is better to set the tighten the bound here to reflect what can actually be chosen. So no, it is not necessary, but having 1.3.1.1 is confusing, and therefore I think we should get rid of it.

@maksbotan
Copy link
Contributor

I've revised (hopefully) everything on Hackage except servant-auth.

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