fix(abg): Use the release date of the latest version for lastUpdated
This makes the metadata file content more stable and allows to provide a checksum, as Kotlin for example is quite unhappy if it finds no checksum or cannot successfully verify it.
Without this every request would produce a different file and thus also a different checksum file, so the checksum would never match the file contents.
This stack of pull requests is managed by Graphite. Learn more about stacking.
Join @Vampire and the rest of your teammates on
Graphite
Can you show me how to reproduce Kotlin being unhappy by the lack of the checksum/release date? I experienced it for version-specific artifacts, but for this artifact I didn't.
If you use a version range, it downloads the metadata file to get the list of versions and wants to validate it, then cries if it cannot.