API: Consider delivering _info_ level annotation in separate JSON array about prometheus HOT 5 CLOSED

yup adding a new field (array or not) in a JSON is not a breaking change and it won't break old client consuming the prometheus API.
So it will be up to the user/developer to update their client to consider this new JSON field.

On Perses side, we are displaying the first warning message if there is one. In case there is a new field info, we will just have to update this code to consider this new information.

And since it's an optional field, then the code is retro-compatible and can work with previous Prometheus version.

So there is no issue to update a client (and UI) to be compatible with the last Prometheus version and then used with a n-1 version

from prometheus.

I'll work on this as discussed

from prometheus.

#14327 has added the additional key, but we still need to update the documentation, see https://github.com/prometheus/prometheus/blob/main/docs/querying/api.md

from prometheus.

@beorn7 My stab at the docs for it: #14429

from prometheus.

Aaaaand it's done. Thanks @zenador and @juliusv .

from prometheus.