Replies: 5 comments 1 reply
-
|
Hi @nscuro If we are using the API to capture data, will the call and data being returned be changing? I cannot see anything in the about changes in v5 document? (Other than pointing to the new server/port) If we were to start from scratch, I am guessing that I can drop the specific PostgreSQL docker image that you helped me set up as that will now be built into it? Great work!!!!! |
Beta Was this translation helpful? Give feedback.
-
|
The API surface remains largely intact, with only a few changes. The APIs that clients are (I think) most likely to use in particular are still there. We include the OpenAPI spec in our documentation now, so you can check for yourself whether everything you need is still there: https://dependencytrack.github.io/docs/next/reference/api/v1/ (you may need to reload the page once when the UI doesn't render completely at first). But I will also compile a full list of changes that may not be as obvious to see. |
Beta Was this translation helpful? Give feedback.
-
|
Breaking changes to the REST API are now documented here: https://dependencytrack.github.io/docs/next/reference/api/v5-breaking-changes/ |
Beta Was this translation helpful? Give feedback.
-
|
We are progressing through the v5 cutover process. As per the announced tag policy, the following changes are now in effect:
v5 images are also available through the GitHub Container Registry, in addition to the usual Docker Hub channel:
Next up, there will be at least one release candidate (RC) release for v5 apiserver and frontend, before the final GA release is cut. |
Beta Was this translation helpful? Give feedback.
-
|
v5 cutover successfully executed. Code has been pushed to the
The old A 5.0.0-rc.1 release has been cut:
Will let this simmer for a few days while we sort out the remaining organizational work. Until then, we'll ship any fixes via successive RC releases. |
Beta Was this translation helpful? Give feedback.
-
|
The following repos are now archived for good:
Remaining issues from the The corresponding Docker Hub repositories are also archived: |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
As some of you may know, we have been building the next major version of Dependency-Track, version 5, under the code name Hyades for quite a while.
We have finally reached the point where we believe version 5 to be ready for prime time. I won't repeat the full list of changes here, instead I'd encourage you to check out the About changes in v5 documentation.
From the platform becoming horizontally scalable, over a new CEL-powered policy engine, to Portfolio Access Control graduating from its beta status, there is a lot of goodness in v5 that we hope you will enjoy.
Outside of what has already changed, we think that this next major version will provide a solid foundation for us to build upon for what's to come next.
There will be a full release announcement together with the official GA release of course, so I'll stop here with the marketing fluff.
This post's primary purpose is to inform you about:
We have assembled a document with all changes you should be aware of, and actions you may need to take, as we progress with the v5 GA release. You can find this document here.
Important
As per the phases section, the
masterbranches of DependencyTrack/dependency-track and DependencyTrack/frontend are now effectively frozen. What this means for contributors is documented here.You can track the GA cutover process via #6102.
If you have any questions or concerns, please direct them to:
#proj-dependency-trackchannel in the OWASP Slack space (invite here)We ask you to consult the document linked above before asking questions. We're also happy to update the document with any feedback you may have.
Cheers,
Niklas
Beta Was this translation helpful? Give feedback.
All reactions