eccodes_jll version in Project.toml

[juliohm]

Is there a strong reason to fix the version as eccodes_jll = "~2.36"? It is holding updates in related packages.

[Alexander-Barth]

See also this:
#35
and in particular
#35 (comment)

It is questionable whether eccodes_jll follows semantic versioning when variables short names are changed in minor releases. Changing the short names will break a lot of code on the user side.

It is rather surprising that Julia's package manager decides to downgrade 7 packages just to upgrade a single one (eccodes_jll) as shown here:
JuliaGeo/NCDatasets.jl#305 (comment)

I am wondering if not all GRIBDatasets.jl releases should be marked as only compatible with eccodes_jll = "~2.36" to avoid this.

[juliohm]

@tcarion what do you think we should do here?

[tcarion]

The easiest solution would be to pin the dependency to the new version of eccodes_jll = "~2.45". Again, the tests fail because some short names have changed again. So I'll need to update the tests and make a breaking release of GRIBDatasets.

I think making a breaking release of GRIBDatasets each time eccodes change its standard is not the most viable solution. A better solution would be to maintain a mapping of legacy names to current identifiers for backward compatibility, but it can be tedious to maintain.