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

Bump chrono to 0.4 #960

Merged
merged 1 commit into from
Jun 22, 2017
Merged

Bump chrono to 0.4 #960

merged 1 commit into from
Jun 22, 2017

Conversation

Eijebong
Copy link
Member

This allow the usage of serde 1.0 with diesel again since chrono 0.3.1 has been
yanked.

@Eijebong Eijebong changed the title Allow chrono 0.4 usage Bump chrono to 0.4 Jun 21, 2017
@Eijebong Eijebong force-pushed the chrono branch 2 times, most recently from 0e98414 to 5f548b4 Compare June 21, 2017 19:46
@killercup
Copy link
Member

Nice, saw the chrono 0.4 announcement earlier and thought we should bump the dep in diesel asap :)

Should we enable chrono's serde feature when our serde feature is enabled? Can we?

@quodlibetor
Copy link
Contributor

@killercup you mean conditionally depending on chrono's serde feature if Diesel's serde is enabled? I think that would be reasonable, reducing the "why isn't serde working" stumbling block.

It seems like it's possible (stackoverflow example).

@beefsack beefsack mentioned this pull request Jun 22, 2017
@killercup killercup merged commit 78293fe into diesel-rs:master Jun 22, 2017
@Eijebong Eijebong mentioned this pull request Jun 22, 2017
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