Currently, release notes and RSS feed updates are often published after a release has already been deployed to Prod1. For customers who rely on release notes as an early warning system, this timing limits their ability to prepare for UI changes, behavioral updates, or regressions.

When changes reach production before documentation is available, it creates operational risk for large enterprises that need to proactively communicate with internal stakeholders.

Requested Enhancement: Leverage the existing Harness custom banner functionality to provide advance release notifications at least 24 to 48 hours before a release is deployed to production.

Suggested Capabilities:

Publish release notes and RSS updates before Prod1 deployment

Provide a pre-release notification banner within the Harness UI

Offer an opt-in early notification subscription for upcoming releases

Include high-level summaries of UI changes, API changes, and behavioral updates

This will give Enterprise customers time to notify internal teams of upcoming changes, validate automation or workflows that could be affected, prepare support teams for potential questions, and review UI changes before they impact end users.

Advance notification would reduce friction during releases and help customers manage stakeholder expectations more effectively.