Add redirect for release predicate

[steiza]

As requested in in-toto/attestation#319 and detailed in in-toto/attestation#320.

I'm not exactly sure how this should work. I'm assuming that after in-toto/attestation#319 lands, there would be a v1.0.2 release cut of https://github.com/in-toto/attestation/, and then this PR should land?

Definitely open to feedback here.

[adityasaky]

I think it might be better for predicate redirects to just point to main rather than a specific tag. This is because the predicates are versioned separately anyway. We can merge this after the PR for the predicate is merged?

cc @in-toto/attestation-maintainers

[marcelamelara]

Yes, I agree that the predicates links should point to main, rather than a version tag. This also avoids having to keep re-specifying predicate URLs on each new spec-wide release tag. I'll update my PR on the /attestation end as well.

+1 to merging after the predicate PR is merged.

[marcelamelara]

Hi, bumping this PR as the final requirement (merge of the related PR) was met a while ago. Thanks!

[chalin]

All: can someone submit an official review for this PR?
@JustinCappos @lukpueh - can this be merged?

[chalin]

By the way, are any of these redirects actually used (I don't see them in the website files), and if so, where?

[marcelamelara]

By the way, are any of these redirects actually used (I don't see them in the website files), and if so, where?

These redirects point to corresponding files in another repo: https://github.com/in-toto/attestation/tree/main/spec/predicates

These are spec files for different types of in-toto metadata, so the purpose of the redirects is to make the schema resolvable from any metadata file.