bug: use the correct format for "expires" (should not include milliseconds) about go-tuf-metadata HOT 3 CLOSED

The way I've read the spec is that fractions are not allowed and IIRC python-tuf API strips them out when expiry is set and does not accept fractions when deserializing JSON (but I could be wrong on the last bit)

from go-tuf-metadata.

Thanks! Apparently we have to update the way we format and store this then 👍

I checked root-signing and I see that at some point go-tuf was generating metadata like that -

https://github.com/sigstore/root-signing/blob/ca9c5644c3217886b543265bacea774351bc0bde/repository/repository/1.root.json#L27C3-L27C3

but eventually it switched to -

https://github.com/sigstore/root-signing/blob/ca9c5644c3217886b543265bacea774351bc0bde/repository/repository/root.json#L6.

I'll update the issue's title so we can track this fix here 👍

from go-tuf-metadata.

closing in favour of theupdateframework/go-tuf#596

from go-tuf-metadata.