Simone Busoli

https://github.com/dependabot/fetch-metadata/pull/270. This PR has a compatibility score badge 95% in the body of the PR, but the output of the fetch-metadata action shows compatibility score 0. https://github.com/nearform/the-fastify-workshop/actions/runs/3180518436/jobs/5184208481#step:2:23

Understood. We need to think about this a little bit though, in terms of the workflow. I mean, if you set a score value and it's not satisfied, what happens?...

I think we're blocked here for the moment, as we didn't quite figure out how to make this work over time. Meaning, reassessing the PRs if and when the compatibility...

Is this really still open?

Thanks and no rush, I was really just playing around with it.

@dependabot recreate

@dependabot recreate

This is now solved in v4, by upgrading to the latest lru-cache which, by now, has removed the browser specific export

@Eomm @climba03003 you may want to take a look at the implementation we're putting together here https://github.com/nearform/fastify-constraints/pull/1

We have built https://github.com/nearform/optic-release-automation-action which we are now using to release our packages, gh actions and applications