Repository navigation
feat(dependency-track): tag new project versions as library - #21
Merged
Merged
Conversation
The policies of Dependency-Track are assigned by tag, and what we publish as open source is a library to the sites that install it. The upload sends projectTags, by default "library"; project-tags takes another list. Dependency-Track only applies them when the upload creates the version.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The policies of Dependency-Track are assigned by tag. What we publish as open source (the WordPress plugins and other public repositories) is a library to the sites that install it, so its findings are judged differently from a site we run.
What changes
dependency-track-upload.ymlhas a new input,project-tags, which defaults tolibrary. The callers don't change.upload.shsends it asprojectTags(comma-separated, as the OpenAPI of the instance, Dependency-Track 5.2.0, describes it).Dependency-Track applies tags only when the upload creates the project version. Every release is a new version, so all following releases get the tag. Versions that already exist keep the tags they have.
Verified
upload.shran against a local mock of the token exchange and/api/v1/bom: with the default it sendsprojectTags=library, and with an empty value it leaves the field out. Everything else is unchanged.