Force new build cache from GitHub deployment
Answered
Lenz Weber-Tronic posted this in #help-forum
I'm building a library for Next.js, which means that every new deploy to Vercel will have an updated library in
I found ways of forcing around that for command line deployments or web hook deployments, but not for deployments triggered by the GitHub integration.
Is there any way around that?
node_modules. Now the build cache doesn't seem to notice that and I always have to manually click Redeploy.I found ways of forcing around that for command line deployments or web hook deployments, but not for deployments triggered by the GitHub integration.
Is there any way around that?
2 Replies
Answer
Nice, didn’t know this existed. I will definitely need this at some point