Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conditionally ovewrite attestations #105

Open
aalmiray opened this issue Jun 7, 2024 · 0 comments
Open

Conditionally ovewrite attestations #105

aalmiray opened this issue Jun 7, 2024 · 0 comments
Labels
feature-request New feature or request

Comments

@aalmiray
Copy link

aalmiray commented Jun 7, 2024

This might be tricky if the attestation store is append-only but, in the case of a rolling tag (let's name it early-access) which moves on a given period (let's say every push to main) the associated release points to the latest artifacts.

At the moment the attestations tab contains all attested artifacts according to the timeline, even if the artifact names are identical, see for example

https://github.com/jreleaser/jreleaser/attestations/1014782
https://github.com/jreleaser/jreleaser/attestations/1013783

In specific case for JReleaser's early-access release the tag & release overwrite any previously existing tag & release, thus there's only one active version of artifacts related to early-access. It would be good if attestations could also be overwritten. Due to the nature of attestations I suppose this behavior (if provided) should be guarded by a conditional flag and disabled by default.

@bdehamer bdehamer added the feature-request New feature or request label Jun 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants