Conversation
WalkthroughEnables the Eclipse “releases/latest” repository by default in the product configuration by changing its enabled flag from false to true. No other repositories or configuration entries are altered. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Suggested reviewers
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches
🧪 Generate unit tests
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 |
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (1)
releng/com.espressif.idf.product/idf.product (1)
96-96: Give the repo a friendly name for UI clarity.Empty name renders poorly in “Manage”/p2 dialogs.
- <repository location="https://download.eclipse.org/releases/latest/" name="" enabled="true" /> + <repository location="https://download.eclipse.org/releases/latest/" name="Eclipse Releases" enabled="true" />
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
releng/com.espressif.idf.product/idf.product(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
- GitHub Check: build_macos
- GitHub Check: build
- GitHub Check: build_windows
🔇 Additional comments (1)
releng/com.espressif.idf.product/idf.product (1)
96-96: Verify target-platform compatibility and update behavior across OSes.releng/com.espressif.idf.product/idf.product currently enables http://download.eclipse.org/releases/latest/ (repositories block — lines ~95–97); the target file pins https://download.eclipse.org/releases/2025-03/ (releng/com.espressif.idf.target/com.espressif.idf.target.target). Manifests also pin CDT bundles (e.g., bundles/com.espressif.idf.ui/META-INF/MANIFEST.MF: org.eclipse.cdt.core;bundle-version="9.0.0").
- If enabling releases/latest is unintended: disable it or replace with a pinned release URL in releng/com.espressif.idf.product/idf.product.
- If intentional: validate p2 update prompt / auto-update behavior on Windows, Linux and macOS to ensure Platform/CDT will not be upgraded beyond tested versions (check restart/privilege flows).
- Cross-check product features vs target definition and bundle-version pins (releng/com.espressif.idf.target/... and bundles/*/META-INF/MANIFEST.MF) before release.
| <repositories> | ||
| <repository location="https://dl.espressif.com/dl/idf-eclipse-plugin/updates/beta/" name="" enabled="false" /> | ||
| <repository location="http://download.eclipse.org/releases/latest/" name="" enabled="false" /> | ||
| <repository location="http://download.eclipse.org/releases/latest/" name="" enabled="true" /> |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
|
@sigmaaa hi! Tested under: eclipse product latest update site enabled ✔️ @alirana01 @kolipakakondal please, review |
|
The only problem could be that as soon as Eclipse pushes an update to a newer version, Espressif-IDE will prompt you to update. However, we are not sure whether our plugins are compatible with the latest version or not |

Description
This should make the process of updating the Espressif IDE smoother and will not negatively affect the user experience
Fixes # (IEP-1636
Type of change
Please delete options that are not relevant.
How has this been tested?
Go to Help -> Install New Tools -> Manage -> check if eclipse product latest update site is enabled
Test Configuration:
Dependent components impacted by this PR:
Checklist
Summary by CodeRabbit
New Features
Chores