v5.0.5

What's Changed

• fix: isolate named client scopes and mixed registration collisions by @melroy89 in #203

Named clients registered in a child scope no longer leak to the parent or sibling scopes: a child now gets its own registry that inherits the parent's clients. As a consequence, in a child scope fastify.mysql may be a copy of the parent's client object (the underlying pool/connection is still shared). Registering __proto__ as a name after an unnamed client is now safe and duplicates are detected.

Full Changelog: v5.0.4...v5.0.5