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

Upgrade to HsYAML-0.2 #5704

Closed
wants to merge 2 commits into from
Closed

Upgrade to HsYAML-0.2 #5704

wants to merge 2 commits into from

Conversation

vijayphoenix
Copy link

Minor changes in code to support HsYAML-0.2 API
HsYAML-0.2 will be released very soon.

@mb21
Copy link
Collaborator

mb21 commented Aug 23, 2019

Thanks! Unfortunately the build seems to be failing for stack-ghc-8_6?

@vijayphoenix
Copy link
Author

Thanks! Unfortunately the build seems to be failing for stack-ghc-8_6?

I forgot to add new dependencies in stack.yaml

@jgm
Copy link
Owner

jgm commented Aug 23, 2019

Thanks! I'll wait til 0.2 is released before merging (and then the stack.yaml and cabal.project will need to be updated).

Does 0.2 include a YAML builder/emitter? That would allow me to replace the yaml package in pandoc-citeproc, as well.

@jgm jgm added this to the 2.8 milestone Aug 23, 2019
@jgm jgm removed this from the 2.8 milestone Sep 3, 2019
@jgm
Copy link
Owner

jgm commented Sep 18, 2019

@vijayphoenix what is the estimated release date for HsYAML 2.0?

@hvr
Copy link
Contributor

hvr commented Sep 18, 2019

@jgm I'd tentatively say the ETA is the upcoming weekend

@vijayphoenix
Copy link
Author

@vijayphoenix what is the estimated release date for HsYAML 2.0?

@jgm HsYAML-0.2 is out.

@jgm jgm closed this in b64410f Sep 22, 2019
@jgm
Copy link
Owner

jgm commented Sep 23, 2019

@vijayphoenix and @hvr thanks for your work on this. I haven't yet had a chance to explore the new features, but it looks very good.

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.

None yet

4 participants