Cache invalidation on plugin upgrade with optional metadata

Hi there, I have an external plugin that I use, and when I update it, I would like to invalidate the cache. This was discussed and implemented in ESLint. This was originally shot down in prettier since there was no obvious way to do it. Can prettier allow the same thing? An optional meta field that can be exposed by plugins, and then pulled into the cache key logic?

E.g. let plugins define some information about themselves, that doesn't need to be read from a package.json.

    meta: {
        name: "eslint-plugin-custom",
        version: "1.2.3"
    }