Update docker.io/dependencytrack/apiserver Docker tag to v5.0.5

Share
Update docker.io/dependencytrack/apiserver Docker tag to v5.0.5
Photo by MICHAEL CHIARA / Unsplash

No problems upgrading the backend Docker container with a Docker compose yaml file within Portainer and by means of Portainer DevOps resp. GitOps with dependency update facilitated by Mend's Renovate Bot.

This MR contains the following updates:

Package Update Change
docker.io/dependencytrack/apiserver (source, changelog) patch 5.0.45.0.5

Release Notes

DependencyTrack/dependency-track (docker.io/dependencytrack/apiserver)

v5.0.5

Compare Source

[!IMPORTANT]
Please read the upgrade notes before upgrading your instance.

What's Changed

Enhancements 🚀
  • Backport: Leverage OSV's modified_id.csv list for full archive downloads by @​nscuro in #​7073
Bug Fixes 🐛
  • Backport: Fix teams being logged as object references instead of names by @​nscuro in #​7059
  • Backport: Fix 500 in /v1/vulnerability/component/{uuid} when a project has >1 analysis for the same vuln by @​nscuro in #​7060
  • Backport: v4-migrator: Fix unique constraint violation on duplicate OIDC group mappings by @​nscuro in #​7061
  • Backport: Fix unassigned severity missing from component metrics by @​nscuro in #​7062
  • Backport: Fix component license name not being returned by v2 component APIs by @​nscuro in #​7063
  • Backport: Fix POLICY_VIOLATION notification templates referencing nonexistent policyCondition field by @​nscuro in #​7064
  • Backport: Fix notification templates referencing nonexistent variables by @​nscuro in #​7069
  • Backport: Fix conversion of OSV version ranges by @​nscuro in #​7072
Dependency Updates 🤖
Other Changes

Full Changelog: https://github.com/DependencyTrack/dependency-track/compare/5.0.4...5.0.5

Read more

Me on Mastodon - This link is here for verification purposes.