Middleware context changes aren't applied to `responseMeta(opts)` options

In our middleware I extend the ctx like this: 
const public = t.middleware(async ({ next, ctx }) => {
    return next({
        ctx: {
            enableCache: true,
        },
    })
})
const public = t.middleware(async ({ next, ctx }) => {
    return next({
        ctx: {
            enableCache: true,
        },
    })
})
and then in the api handler where I'd like to add cache headers in the reponseMeta function I try accessing ctx. However it hasn't been modified there and returns an empty object. Accessing ctx in my router procedure itself properly returns the right context. 
export default trpcNext.createNextApiHandler({
  router: appRouter,
  createContext,
  responseMeta(opts) {
    console.log(opts);
    return {};
  },
});
export default trpcNext.createNextApiHandler({
  router: appRouter,
  createContext,
  responseMeta(opts) {
    console.log(opts);
    return {};
  },
});
Any idea on how I can get this to work? Thank you!
More Posts
Cookie authentication flowHello can i get a bit of a help and explanation please? Im frontend learning backend on trpc, I haveIs It Possible to use methodOverride with createNextApiHandler?I'm trying to build queries for grids and filter and sort object could get very large which is exceeLambda container reuseIn high traffic environments lambda reuses the same container to serve multiple requests. The lambdaTrouble with Vercel and deployment URLHey I've been having a problem with nextjs deploying to vercel. In localhost the calls to the backen