Skip to content

Conversation

@XuechunHou
Copy link
Contributor

No description provided.

@XuechunHou XuechunHou self-assigned this Sep 21, 2025
@jefferbrecht
Copy link
Member

VSAs are a release artifact, so shouldn't they be published as releases instead, e.g. using immutable GitHub Releases? This directory is going to grow unbounded and, notably, the VSA for version X won't actually be available at the commit tagged for X, which limits its usefulness.

If these absolutely do need to be committed to the source tree, then can we put VSA under a new root directory called e.g. meta or attachments or something, since we might publish other non-VSA documents later too, so that the root directory doesn't get too cluttered?

@XuechunHou XuechunHou closed this Sep 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants