The previous release used the "-full" renovate image which is 6 gigabytes
but doesn't install tools at runtime. Apparently the docs discourage this, so
this release moves to using the "non-full" image.
When renovate detects e.g. a golang dependency, it will now download a golang toolchain
and store it in a persistent volume. This means the total disk usage of the tool should
be much lower for most users (the smaller image is still 1.26GB).
The previous release used the "-full" renovate image which is 6 gigabytes
but doesn't install tools at runtime. Apparently the docs discourage this, so
this release moves to using the "non-full" image.
When renovate detects e.g. a golang dependency, it will now download a golang toolchain
and store it in a persistent volume. This means the total disk usage of the tool should
be much lower for most users (the smaller image is still 1.26GB).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The previous release used the "-full" renovate image which is 6 gigabytes
but doesn't install tools at runtime. Apparently the docs discourage this, so
this release moves to using the "non-full" image.
When renovate detects e.g. a golang dependency, it will now download a golang toolchain
and store it in a persistent volume. This means the total disk usage of the tool should
be much lower for most users (the smaller image is still 1.26GB).
63b10b570bto121b255f47👏
@@ -11,3 +11,3 @@- "swarm.cronjob.enable=true"- "swarm.cronjob.schedule=${CRON_SCHEDULE}"- "coop-cloud.${STACK_NAME}.version=1.0.1+41-full"- "coop-cloud.${STACK_NAME}.version=1.0.1+41"Do we need to bump the
1.0.1part also?I planned to do a
syncon main (I probably should have just not changed the line at all)