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

cryptol-remote-api: Restore the ability to build with vector-0.12.* #1506

Merged
merged 1 commit into from
Mar 13, 2023

Conversation

RyanGlScott
Copy link
Contributor

The downstream saw-remote-api library doesn't quite support vector-0.13.* yet, but #1499 accidentally restricted cryptol-remote-api's build plan to only allow vector-0.13.*. This restores the ability to build cryptol-remote-api with vector-0.12.* for saw-remote-api's sake.

The downstream `saw-remote-api` library doesn't quite support `vector-0.13.*`
yet, but #1499 accidentally restricted `cryptol-remote-api`'s
build plan to only allow `vector-0.13.*`. This restores the ability to build
`cryptol-remote-api` with `vector-0.12.*` for `saw-remote-api`'s sake.
@RyanGlScott RyanGlScott requested review from yav and kquick March 10, 2023 18:57
Copy link
Member

@kquick kquick left a comment

Choose a reason for hiding this comment

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

I assume there's nothing specific to vector 0.13 that was needed.

@RyanGlScott
Copy link
Contributor Author

I assume there's nothing specific to vector 0.13 that was needed.

Nope, it was only done for the sake of getting a version of vector whose version bounds permit building with GHC 9.4.

@RyanGlScott RyanGlScott merged commit 9382d52 into master Mar 13, 2023
@RyanGlScott RyanGlScott deleted the vector-0.12-restore branch March 13, 2023 18:02
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.

2 participants