New version: Interpolations v0.12.3

[JuliaRegistrator]

• Registering package: Interpolations
• Repository: https://github.com/JuliaMath/Interpolations.jl
• Created by: @timholy
• Version: v0.12.3
• Commit: e1a170ad1663218dad94fc68958f1bdac60f268c
• Reviewed by: @timholy
• Reference: JuliaMath/Interpolations.jl@e1a170a#commitcomment-35522746

[ghost]

Your new version pull request does not meet all of the guidelines for automatic merging.

Specifically, your pull request does not meet the following guidelines:

• The following dependencies do not have a compat entry that has an upper bound: OffsetArrays, StaticArrays, Ratios, AxisAlgorithms, WoodburyMatrices

---

It is important to note that if your pull request does not meet the guidelines for automatic merging, this does not mean that your pull request will never be merged. It just means that your pull request will require manual review by a human.

These guidelines are intended not as requirements for packages but as very conservative guidelines, which, if your new package or new version of a package meets them, it may be automatically merged.

---

On a separate note, I see that you are registering a release with a version number of the form v0.X.Y.

Does your package have a stable public API? If so, then it's time for you to register version v1.0.0 of your package. (This is not a requirement. It's just a recommendation.)

If your package does not yet have a stable public API, then of course you are not yet ready to release version v1.0.0.

---

[noblock]

[julia-tagbot]

I've created release v0.12.3, here it is.

[fredrikekre]

Please add compatibility bounds for the next release such that it will be automatically merged.

[timholy]

Is there a solution for JuliaRegistries/Registrator.jl#122?

[fredrikekre]

Not really, no.

[timholy]

Will do it for simple ecosystems then, but not for complicated ones---the amount of time lost to debugging version incompatibilities is too high. I apologize in advance for the burden on the Registry maintainers!

[fredrikekre]

No worries. I think it should be relatively easy to automate it so maybe I will write something for that issue some day.