trigger Vercel docs build when a new release is deployed

[rafaelcr]

so docs can be updated without the need for a manual Vercel build

[LakshmiLavanyaKasturi]

This is dependent on the decision made for remote docs - hirosystems/docs#356. @rafaelcr @CharlieC3

[CharlieC3]

@LakshmiLavanyaKasturi Is this still needed? Can it be closed?

[LakshmiLavanyaKasturi]

I see an issue with the build cache. It looks like, Netlify is picking the old cache, and the deployment still fails after refreshing the build using the "redeploy" button from Vercel.

Eg, In the PR: hirosystems/docs#401, there were remote file changes, and I tried to use "redeploy" from Vercel to pull the remote changes. However, the Vercel and Netlify deployments failed as they showed the old cache.

When I pushed a new commit to the branch, the deployment was successful. @CharlieC3

[chresko]

@LakshmiLavanyaKasturi Can this be closed? Thanks!

[rafaelcr]

We should still write this automation. Now that we have automatic OpenAPI updates in the docs repo (thanks to hirosystems/docs#525), we should just make sure that whenever a release is made in any API that we trigger the docs Vercel build again so the new API definitions are refreshed automatically.

[CharlieC3]

@rafaelcr I submitted three PRs to address this here:
hirosystems/stacks-blockchain-api#1787
#285
hirosystems/token-metadata-api#192