Closed tomchor closed 3 years ago
Yes, good catch. LESbrary.jl isn't a registered package so we can definitely get away with using a "^0"
compat entry.
I'll remove the [compat]
entries on a different branch. Should probably also get rid of CompatHelper and TagBot until we want to register LESbrary.jl as a proper package. I'll also update LESbrary.jl to use the latest version of Oceananigans.jl
Ah so LESbrary.jl depends on Oceanostics.jl but I just noticed you already updated the compatibility there!
Should probably also get rid of CompatHelper and TagBot until we want to register LESbrary.jl as a proper package.
So, why not register it as a proper package?
Ah so LESbrary.jl depends on Oceanostics.jl but I just noticed you already updated the compatibility there!
Yes! Although I am now realizing that I will probably need to release a new version there for this change to "take effect". I gotta figure out how to do that haha
Ah found a place that could be used to tag a new version: https://github.com/tomchor/Oceanostics.jl/commit/8359a430a6e1ff088850d8a666a7cd32b33548a3
So, why not register it as a proper package?
Hmmm, not sure. I guess LESbrary.jl still feels a little rough and has some heavy dependencies. I think we should resolve #66 and get rid of the Plots.jl and CairoMakie.jl dependencies before registering it as a new package. They're not even really used by LESbrary.jl, just by the "examples".
Oceananigans is changing versions extremely fast. Maybe it's worth changing the Oceananigans
[compat]
entry to something like "^0"? So that every version until1.0
will in principle be supported?