The docker/build-and-push-action we are using in the workflow to build the images does some automatic caching by default. Nonetheless, that feature seems to be somewhat experimental, and I am afraid it may not be appropriate for what we are doing here. Particularly, I am afraid caching will occur in situations where it should not be happening, like when we update the dependencies of the package. The simplest solution is to set no-cache: true (which is false by default).
The docker/build-and-push-action we are using in the workflow to build the images does some automatic caching by default. Nonetheless, that feature seems to be somewhat experimental, and I am afraid it may not be appropriate for what we are doing here. Particularly, I am afraid caching will occur in situations where it should not be happening, like when we update the dependencies of the package. The simplest solution is to set
no-cache: true(which isfalseby default).