Adam Shiervani eebf332bc0 fix: keep default release when latest has no compatible SKU artifact ...

After the getDefaultRelease SKU-compat fix, the default path was
graceful but the rollout-upgrade path stayed strict: if a device was in
the rollout bucket and the latest release lacked a compatible artifact
for the requested SKU, dbReleaseToMetadata still threw and 404'd the
whole request — even though responseJson already held a valid default.

Short-circuit the upgrade when the latest release has no compatible
artifact and update the regression test to assert the default is kept
instead of asserting the throw.

2026-04-27 20:01:56 +02:00

..

releases.test.ts

fix: keep default release when latest has no compatible SKU artifact

2026-04-27 20:01:56 +02:00

setup.ts

Add SKU-aware OTA release artifacts (#56)

2026-04-27 19:18:54 +02:00

sync-releases.test.ts

Add SKU-aware OTA release artifacts (#56)

2026-04-27 19:18:54 +02:00