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

Handling of Latest Version for Snapshots #323

Open
msymons opened this issue Nov 7, 2022 · 0 comments
Open

Handling of Latest Version for Snapshots #323

msymons opened this issue Nov 7, 2022 · 0 comments

Comments

@msymons
Copy link
Member

msymons commented Nov 7, 2022

Current Behavior:

Dependency-Track displays a yellow (warning) icon when a component is not the latest version. This icon is also displayed for a snapshot version of a component that is more recent than the "latest version"

image

Steps to Reproduce:

This should be easy to reproduce by uploading a BOM from a feature/dev branch of a multi-module maven project... the modules should all then be snapshot versions that will have a later version number than the latest release for the project.

Expected Behavior:

When latest > release, then do not indicate that the component is out of date. Indicate something else.
Ideally I would like to see an entirely different icon displayed. Per #311... different colour and different shape.

If this could be applied to snapshots generically then it would also capture a use case that I have seen: where project X has component X.Y that is used in project Z. A developer makes changes to X.Y and then "tries out" the snapshot in project Z (possibly X has rubbish tests and Z has excellent tests). Then they do a release of Z forgetting to include a release version of X.Y. Having a unique "version status" icon and being able to sort by "version status" (logged as #322) would make it easy to see when a project has this kind of problem.

Environment:

  • Dependency-Track Version: 4.6.1 (although I tested using 4.7 SNAPHOT due to authentication fix).
  • Client Browser: N/A
  • Client O/S: N/A
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant