v17.1.1

8ffdba7 (Remove memory healthcheck, 2025-06-06)

v17.1.0

4558b5a (Bump docker-progress to v5.3.1, 2025-05-13)
0af915d (Pass AbortSignal to image pull functions, 2025-05-14)
8c69166 (Support target state apply cancellation, 2025-05-14)

v17.0.5

49e91a2 (Exclude reclaimable slab memory from used memory metric, 2025-05-25)

v17.0.4

4318272 (Remove unsupported fields from contract requirements, 2025-05-15)

v17.0.3

7c83eae (Simplify contract validation module, 2025-05-08)

v17.0.2

d475b1d (Fix search for app leftover locks, 2025-04-01)

v17.0.1

caed4dc (Clarify firewall docs on behavior with host network containers, 2025-03-25)

v17.0.0

Add Docker network label if custom ipam config

This release resolves a bug where a target release with only a network custom IPAM config change does not get applied by the Supervisor.

When receiving a target release with a custom IPAM config, the Supervisor will add the io.balena.private.ipam.config label to Docker networks with custom IPAM configs. As a result, these networks will be properly recreated.

This is a major change. Devices that currently have services using networks with custom IPAM configurations will experience:

• A one-time service restart for services dependent on the custom network
• Recreation of affected networks to apply proper IPAM configuration

List of commits

b596c77 (Add Docker network label if custom ipam config, 2025-01-29)

v16.12.9

7764f98 (Start a dependent if all dependencies are started, 2025-03-20)

v16.12.8

bdbc6a4 (Ensure poll socket timeout is defined early, 2025-03-12)
ae337a1 (Remove GOT retries on state poll, 2025-03-11)