RDK0002 — Asset loss

Severity: warning · Command: redecker inspect --from

An upgrade drops a target framework under lib/, or a runtime identifier under runtimes/, that the previous version shipped.

Why it is a warning

Losing an asset is not automatically wrong. Packages legitimately retire dead platforms, and holding an upgrade back because it stopped shipping something nobody targets would be noise.

But it silently changes what a consumer gets:

• A project multi-targeting net48 discovers a dropped lib/net461 asset only when compilation quietly picks a different one
• A project shipping a win-arm build discovers a dropped RID at run time, on that device

Redecker cannot know which of your targets matter, so it reports what changed and leaves the decision with you. That is the difference between a warning and an error here.

Example

$ redecker inspect SQLitePCLRaw.lib.e_sqlite3 --from 2.1.11 --to 2.1.12
warning RDK0002: 2.1.11 to 2.1.12 drops 5 runtime identifiers:
    win-arm, win10-arm, win10-arm64, win10-x64, win10-x86

Worth noting from that real case: the upgrade also triggered RDK0001, because the package dropped win-arm from runtimes/ while its targets file still copied it. The two rules caught the same underlying mistake from different directions — one as a hard breakage, one as a platform you may have been relying on.

Requires --from

This rule compares two versions, so it only runs when you tell inspect which version you are coming from.