3 ms·
Yes, they can. The thing is that tarballs are not part of release artifacts, even though they do appear to be among them. If you look closely, even the endpoint
by friendzis 4y ago
Yes, they can. The thing is that tarballs are not part of release artifacts, even though they do appear to be among them. If you look closely, even the endpoints that user uploaded artifacts and generated tarballs point to are different.
Github could just generate the tarball once and store it in the same way as other release artifacts. But for some reason they chose not to.
- usr1106 4y agoSome reason? Storage is not free after all and many tarballs won't be fetched frequently I'd assume.
- DelightOne 4y agoTo clarify: I am proposing to use the old archival method for already-existing releases, for example by passing in the necessary arguments to git archive forever. Releases without previous archival or created after some point in time in the future call git archive with the new arguments. No substantially more storage should be necessary. Once the accompanying gzip-version is sufficiently old or unsafe, breaking very old releases does not matter anymore, making it a seamless transition.