Epic Goal

• Update the OCP Console frontend React dependency to a more recent version, as the current version has been end-of-life for over a year.

Why is this important?

• The longer we wait to make this update, the harder it will be. It's important to stay current so that we can be more nimble with tech debt and dependencies.

Scenarios

1. As a developer, I am assigned a high-priority feature. I find that React must be updated as part of the feature. I also find that because there are many breaking changes between our version and the latest, an update would be out of scope for this story. The feature must be deferred until we can address the tech debt.
2. A major issue is found in our current version of React, and an update is required. The scope of this update work has ballooned over the time since our last update. We have to drop other important work to prioritize this update and again, other important features or work are deferred.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• OCP Console React dependency and all other tangential dependencies have been updated to an agreed-upon recent version.
• Other stakeholders, like plugin consumers, should not be affected by this change.

Previous Work (Optional):

1. https://issues.redhat.com/browse/CONSOLE-3316

Open questions:

1. Should this be accomplished as a swarm activity where we spend a sprint addressing all blockers?
2. Should we take a cautious approach and resolve blockers over time until we reach a point where an update is feasible?

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>