Chapter 2. Breaking changes


This section lists breaking changes in Red Hat Developer Hub 1.5.

Previously, configuring the sign-in resolver to bypass user provisioning in the Developer Hub software catalog required setting dangerouslyAllowSignInWithoutUserInCatalog: true at the root of the app-config.yaml file.

In this release, the previous root level configuration has been moved to the resolver level. For more details, see Authentication in Red Hat Developer Hub.

Additional resources

The scopes parameter is now mandatory for the gitlab:projectDeployToken:create action. A valid value, such as ['read_repository'], must be provided.

Additional resources

The dynamicPlugins.cache.volumeClaimSpec field has been removed from values.yaml, making dynamic plugin storage ephemeral by default. If you want to enable plugin caching persistence, you must now manually configure a PersistentVolumeClaim and mount it using the extraVolumes and extraVolumeMounts fields in the Helm chart values.

This change also resolves issues with running multi-replica RHDH deployments, as using a PVC for the Dynamic Plugins cache previously led to potential write conflicts. For more information, see Creating a PVC for the dynamic plugin cache using the Helm Chart.

Additional resources

Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat Documentation

Legal Notice

Theme

© 2026 Red Hat
Back to top