[DevOps]: Next.js caching issue and failed deployments

[ssandino]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

When deploying a pull request (PR) that contains only changes within the 'shared' folder, such as text modifications, the deployment process on Vercel does not detect any changes, leading to the cancellation of the deployment.

Steps To Reproduce

1. Change a text in a text file, commit and deploy

Expected Behavior

The deployment process should not abort when changes are made only in the 'shared' folder, such as text modifications.

Screenshots?

No response

Desktop Environment (please complete the following information)

- OS:
- Browser:
- Version:

Smartphone Type (please complete the following information)

- Device:
- OS:
- Browser:
- Version:

Additional context

Only solution at the moment is to manually restart the deployment on Vercel and deactivating the caching option

Code of Conduct

• I've read the Code of Conduct and understand my responsibilities as a member of the Social Income community

[ssandino]

Work around: manually start deployment in https://vercel.com/social-income/public (needs admin rights)