Chapter 1. New features

Previously, include plugin configuration files would overwrite existing files. With this update, Red Hat Developer Hub will merge configurations from existing include files, only overwriting specific keys while preserving keys defined in existing include files, mirroring the behavior for the plugins key.

As of RHDH 1.7.1, the Orchestrator plugin 1.7.1 is now available.

With this update, Red Hat fully supports the Adoption Insights plugins. These plugins are no longer Technology Preview.

Red Hat Developer Hub 1.7 adds dynamic plugin dependency management, so that the Operator can manage Kubernetes resources required by plugins.

For more information, see Dynamic plugin dependency management

With this update, Orchestrator plugins with dependencies are added to the RHDH profile. The Orchestrator plugin is disabled by default. When you enable the Orchestrator plugin, it will deploy dependencies and work out of the box on RHDH.

With this update, the @redhat-developer/red-hat-developer-hub-theme package is replaced with the plugin version from the rhdh-plugins repository to improve theme integration and visual consistency. Minor UI enhancements include updated border radius on cards.

This release includes several enhancements to improve the usability and consistency of the RBAC experience:

These changes aim to create a more intuitive and seamless role management workflow.

In this release, Developer Hub administrators can configure dynamic plugins directly within the Extensions UI. Administrators can enable, disable, install, or edit the configuration of dynamic plugins on the Extensions Details Page.

This is an opt-in feature that must be enabled by configuration, and it is intended for testing and development environments only; it is not recommended for production use.

This release requires a single replica deployment and uses a persistent volume claim (PVC) for the dynamic plugin configuration file. The Developer Hub backend does not automatically restart when you save configuration changes. You must restart the Developer Hub application for any dynamic plugin configuration updates to take effect.

Backend dynamic plugins have reached General Availability (GA). A new command-line tool, @red-hat-developer-hub/cli (rhdh-cli), has been released for building and packaging these plugins. As a result, the @janus-idp/cli is now officially deprecated. All users should migrate their build processes to @red-hat-developer-hub/cli to maintain support and receive future updates.

RHDH 1.7 introduces the new Administrator Quick Start guide, a feature designed to streamline the initial setup and configuration process for platform engineers. This guided, interactive experience appears automatically on an administrator's first login, providing clear, step-by-step instructions for essential platform tasks. The goal is to significantly reduce onboarding time and help you configure your RHDH instance with confidence.

Quick start tracks your progress, offers context-aware help that follows you across configuration pages, and can be dismissed and reopened from the header at any time. This guide ensures a confident, efficient, and structured onboarding experience. Note that when permissions are enabled, this feature is currently available for administrators only, with support for other roles planned for future versions.

With this release, you can display a user avatar in the profile dropdown in the global header.

With this update, the look and feel of Developer Hub has been updated to better match the visual style of PatternFly 6 and improve alignment with the {company} product portfolio.

RHDH has been enhanced to provide crucial traceability, allowing users to easily identify the template version used to create a specific component. This enhancement helps determine if an older entity needs updating or if a bug is linked to a particular Software Template version.

Scaffolder templates can now be versioned using the backstage.io/template-version annotation and the catalog:template:version action. When used with the catalog:template:version action, the annotation of the template is applied to the generated catalog entity.

Red Hat Developer Hub supports high availability setups in Amazon Elastic Kubernetes Service (EKS). This enhancement allows the deployment to scale beyond a single replica, ensuring the application remains operational and accessible even in the event of failures or disruptions.

For more information, see Configuring high availability in Red Hat Developer Hub.

In this release, the Adoption Insights plugin is fully supported and enabled by default. The Adoption Insights plugin provides key metrics and trends to help you understand Developer Hub usage.

If you have an existing Adoption Insights plugin custom configuration with GitHub Container registry images already set up, you can upgrade to the latest version to omit configurations using GitHub Container registry images. For more information, see Configuring the Adoption Insights in Red Hat Developer Hub.

The Developer Hub community plugins have been updated to Backstage version 1.39.

Previously, the Red Hat Developer Hub would fail to start if a specified include file in dynamic plugins configuration did not exist. This update addresses the issue by logging a warning and skipping the file if it is not found.

Red Hat Developer Hub fully supports the @backstage/plugin-catalog-backend-module-msgraph plugin, which ingests user and group entities from Microsoft Azure Active Directory into the software catalog via the Microsoft Graph API. This populates the catalog with your organization's directory data, ensuring that component ownership is accurately mapped when used with the Microsoft authentication provider.

In this release, the following Home page cards are added:

For more information, see Customizing the Home page cards.