Skip to content
This repository has been archived by the owner on Aug 12, 2022. It is now read-only.

Put Julia version upper bound on a bunch of DataStructures versions #12407

Merged
merged 1 commit into from
Dec 14, 2017

Conversation

martinholters
Copy link
Member

They don't even load on Julia versions>=the new upper bound.

I have no idea regarding the minimum Julia version for DataStructures v0.0.0 --- is 0.0.0 ok in that case?

And we should probably wait with merging this until a new DataStructures version is tagged, as the newest one installable on Julia master would otherwise be v0.2.6 which might result in unpleasant surprises, I could imagine.

They don't even load on Julia versions>=the new upper bound.
@aviks
Copy link
Member

aviks commented Dec 8, 2017

Ok, let us know when this is safe to merge.

@martinholters
Copy link
Member Author

CC @kmsquire Does this look ok to you? Would you mind tagging a new version?

@martinholters
Copy link
Member Author

Alright, new version 0.7.3 tagged, so this should be safe now.

@martinholters martinholters merged commit af3ca3f into metadata-v2 Dec 14, 2017
@martinholters martinholters deleted the mh/datastructures_upperbound branch December 14, 2017 10:50
@kmsquire
Copy link
Member

@martinholters, sorry, working through my Julia backlog and just saw this. Thanks for working through it. It generally seems fine, although I haven't checked all of the versions.

nkottary pushed a commit to nkottary/METADATA.jl that referenced this pull request Dec 29, 2017
…uliaLang#12407)

They don't even load on Julia versions>=the new upper bound.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants