Is relabeling function broken in PMM 2.5.0 April 14?

I readed in:
In the next release, we will use our own code for configuration parser. It is a separate Go library that can be useful for the community.
I have updated today my PMM2 server and i get yml parsing errors:

line 21: cannot unmarshal !!seq into string
line 41: cannot unmarshal !!seq into string
line 43: cannot unmarshal !!seq into string
line 45: cannot unmarshal !!seq into string

That lines are relabeling ones in my custom prometheus configuration file:

[root@3550a92c2086 opt]# cat /srv/prometheus/prometheus.base.yml
- job_name: blackbox80
- http_2xx
scrape_interval: 1m
scrape_timeout: 10s
metrics_path: /probe
scheme: http

- targets:
metrics_path: "/archive"

- source_labels: [__address__]
target_label: __param_target
- source_labels: [__param_target]
target_label: instance
- source_labels: [__param_target]
target_label: node_name
- target_label: __address__

In previous version it worked without problems.
Is it broken, is there another way to do relabeling with that new PMM2 version?

Hello @b4buFr1k
Thanks for bringing this to our attention. I wonder if you would be good enough to report that as a bug via our Jira system? That’s where the engineering team controls their work.  Here’s the link: and there’s some guidelines here that might help. By reporting to Jira you will be kept informed on the bug review and progress through to a fix. If you return here and post the link to the Jira post that would be fantastic and I’ll award you a bug hunter badge… you might be the first to receive it   :D  

I have opened the jira ticket:

Great thank you! Sorry your posts were still being moderated but I will verify your user now. And award you the FIRST EVER Forum bug hunter badge  B)