fix: stale Helm release history after successful rollback#18799
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
✅ Deploy Preview for kubestellarconsole ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
This PR updates the Helm release drilldown to allow the release history to be re-fetched after a rollback, instead of being skipped once cached.
Changes:
- Added a
forceparameter tofetchHistoryto bypass thereleaseHistorycache guard when needed. - Updated the rollback success path to call
fetchHistory(true)to refresh history.
f7f239e to
c5380eb
Compare
|
Scanner note: This PR is from an external contributor (fork), so CI checks (PR Verifier, Build and Deploy) are skipped due to the fork security guard ( A maintainer should review the changes manually and either:
|
|
🔍 Scanner pass — This PR's The code change itself (adding |
Signed-off-by: ashnaaseth2325-oss <ashnaaseth2325@gmail.com>
Signed-off-by: ashnaaseth2325-oss <ashnaaseth2325@gmail.com>
c5380eb to
05c0eb9
Compare
✅ Post-Merge Verification: passedCommit: |
SUMMARY
This PR fixes an issue in the Helm Release drilldown where the History tab continued to display stale revision data after a successful rollback. The change updates the history refresh logic in
HelmReleaseDrillDown.tsxto ensure fresh revision data is fetched when a rollback completes, while preserving the existing caching behavior for normal tab navigation.FIX