I suggest to only release new Docker images if the actual necessary files are altered.
For example, if a dependency update PR is merged that only touches development-necessary files (like updating the development requirements), then a new Docker image shouldn't be released. At least not if the update doesn't have any implications on the core files.
I suggest to only release new Docker images if the actual necessary files are altered.
For example, if a dependency update PR is merged that only touches development-necessary files (like updating the development requirements), then a new Docker image shouldn't be released. At least not if the update doesn't have any implications on the core files.