known_artifacts is an untyped dict passed around the package loaders and loaded from the 'revisions.metadata' column.
AFAICT, it is only ever used to read one value at the end of its journey through the loader.
Instead, this dict should be converted to an ExtId object as soon as possible.
Note that this task isn't about using the extid storage, but is a transitional state we need to smoothly start using the extid storage
| rDLDBASE Generic VCS/Package Loader | |||
| D5290 | rDLDBASEeef74bbfacc0 Deduplicate resolve_revision_from across package loaders | ||
| D5288 | rDLDBASEfdb41abd76b2 nixguix: Split 'integrity' extraction out of resolve_revision_from | ||
| D5289 | rDLDBASE20a3c9c809c0 archive, cran: Replace 'artifact_identity' with extid to detect known packages | ||
| D5286 | rDLDBASEe7ae6364c06a debian: Split original_artifact parsing out of resolve_revision_from | ||
| D5287 | rDLDBASEf827d04cb538 npm, pypi: Split original_artifact parsing out of artifact_to_revision_id | ||
| D5285 | rDLDBASE268f83e943a4 debian: Make resolve_revision_from use the sha256 of the .dsc | ||
now it is. (the mercurial loader technically doesn't use ExtID internally, but it already passes nodeids, which are close enough)