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

docs(schema): clarify purls must not contain versions #317

Closed

Conversation

andrewpollock
Copy link
Collaborator

This clarifies the intent of the optional purl field to refer to the package in an analogous way to the ecosystem and name and not contain any explicit version component.

This clarifies the intent of the optional `purl` field to refer to the
package in an analogous way to the `ecosystem` and `name` and not
contain any explicit `version` component.

Signed-off-by: Andrew Pollock <apollock@google.com>
@@ -668,7 +668,8 @@ within its ecosystem. The two fields must both be present, because the
The `purl` field is a string following the
[Package URL specification](https://github.com/package-url/purl-spec) that
identifies the package, without the `@version` component.
This field is optional but recommended.
This field is optional but recommended. It *must not* contain a `version`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is already made explicit on line 670?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Huh. Couldn't see it for the trees at the time :-(

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.

2 participants