Conversation
📝 WalkthroughWalkthroughThe P2 update site configuration is restructured: ChangesP2 Update Site Restructure
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
AndriiFilippov
left a comment
There was a problem hiding this comment.
@sigmaaa hi !
LGTM 👍
kolipakakondal
left a comment
There was a problem hiding this comment.
Approach seems to be fine and helpful from the code maintenance point of view but we need to make sure it won't introduce any regressions.
I updated IDE v3.1.0 to v4.3.0 using the update site generated by this PR. No issues or regressions were found. I think this is enough since this PR does not cover offline update. |
Description
After deleting the p2 folder and retesting the lightweight online update site, I noticed an issue when updating from older versions that I haven't been able to resolve yet. However, we still need a reliable and robust update site that is easy to maintain and can handle updates from older IDE versions. Therefore, I decided to move the offline update site approach from this PR: #1474 into this one.
Fixes # (IEP-1786)
Type of change
Please delete options that are not relevant.
How has this been tested?
Note: Use the update option
Test Configuration:
Dependent components impacted by this PR:
Checklist
Summary by CodeRabbit