Add deprecation banner to Dependency Proxy for Packages UI directing users to Maven Virtual Registry

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Summary

Add a visible deprecation notice to the Dependency Proxy for Packages UI informing users that the feature is deprecated and will be removed in GitLab 20.0. The notice should direct users to migrate to the Maven Virtual Registry.

Context

The Dependency Proxy for Packages (Maven) has been deprecated as of GitLab 19.1 (breaking change approval). The Maven Virtual Registry is the replacement and is already generally available.

We need an in-product signal so that any user who visits the Dependency Proxy for Packages settings or configuration pages sees a clear deprecation notice before the feature is removed in 20.0.

Requirements

  1. Add a deprecation alert banner to the Dependency Proxy for Packages pages (settings, configuration, and any listing views).
  2. The banner should:
    • Use the warning variant of the GitLab alert component
    • State that the Dependency Proxy for Packages is deprecated and will be removed in GitLab 20.0
    • Recommend users migrate to the Maven Virtual Registry
    • Include a link to the Maven Virtual Registry documentation: https://docs.gitlab.com/user/packages/virtual_registry/
  3. The banner should be non-dismissible (persistent deprecation notice).
  4. The banner should be visible to all users who can access the Dependency Proxy for Packages settings.

Suggested copy

Dependency Proxy for Packages is deprecated. This feature will be removed in GitLab 20.0. We recommend migrating to the Maven Virtual Registry, which provides the same caching functionality with additional features. Learn more about the deprecation.

References

Edited by 🤖 GitLab Bot 🤖