Beth Skurrie

This surprises me, as I didn't think the broker ever supported rendering v3 pacts!

Yes, I would happily accept a PR. Because I can't reproduce this issue myself, I need someone to submit a pact that causes the issue. I don't know which particular...

That would be easily done because it already silently drops completely duplicate publication requests.

Unfortunately, we can't make the resource completely uneditable, because we support PATCH to allow builds using pact to run on multiple nodes, and merge their results at the end.

I haven't had time to go through all of those vulnerabilities individually, however, I have done a bundle update and put out a new docker image with tag `2.98.0.1`, so...

The latest version of nokogiri is already being used in the docker image, so I don't think there's anything we can do to make those go away.

This is probably so out of date as to be irrelevant now. Closing, but feel free to re-open.

The broker isn't making up that text! I'd have a look at the code that is setting your tag in the provider configuration.

I started on this, and got blocked by some issues with a dependency. It's not high on the list, so I would recommend having an intermediate build in the meantime...

It hasn't been a high priority because there is a work around of creating an intermediate build from which you can trigger a downstream build with the right tags. You're...