Sync and update lvgl port component with ESP Componnents Registry (BSP-717)

[andrzejroszkowski]

Board

any

Hardware Description

Any using LVGL

IDE Name

any

Operating System

any

Description

Sync LVGL port component - update version and release it, one that is currently deployed is v2.6.0.

Number of patches applied although version was not updated, neither deployed (registry reports at least 4 months old)

Sketch

any

Other Steps to Reproduce

No response

I have checked existing issues, README.md and ESP32 Forum

• I confirm I have checked existing issues, online documentation and Troubleshooting guide.

[github-actions]

Hi @andrzejroszkowski! Please be aware that (1) the following suggestions are generated by a bot and haven't been fact-checked by Espressif Systems, (2) burning eFuses and enabling security features are irreversible operations and can damage your ESP32 device. We hope that this message will help you until an Espressif Engineer looks at your issue.

---

Thanks for the report — you’re right to notice a mismatch.

What we can confirm from the knowledge sources:

• The ESP Component Registry currently shows espressif/esp_lvgl_port at version v2.6.0, supporting ESP-IDF ≥4.4 and LVGL >=8,<10. [esp_lvgl_port comp]
• The changelog on the Component Registry lists several fixes and features up to 2.6.0 (including touch scaling and ESP32-P4 PPA rotation), with no newer released version listed there. [esp_lvgl_port changelog]
• In the esp-bsp repository, the esp_lvgl_port CHANGELOG shows an Unreleased section with additional items (e.g., option to place LVGL task stack in external RAM; fixed callback for RGB display for IDF6), indicating commits have landed that aren’t yet published as a new Registry release. [esp_lvgl_port repo changelog]

So, it appears there are upstream changes not yet pushed as a new version to the ESP Component Registry. To get those changes into the Registry, the maintainer needs to cut a new release and upload it. The documented flow for publishing to the ESP-Registry is:

1. Create an ESP-Registry token (via the account linked to GitHub), export it as IDF_COMPONENT_API_TOKEN, then
2. Run idf.py upload-component with the proper namespace and name. [Component release guide]

Example:

• idf.py upload-component --namespace espressif --name esp_lvgl_port [Component release guide]

Action requested

• Please sync and publish a new release of espressif/esp_lvgl_port to the ESP Component Registry to include the “Unreleased” changes from esp-bsp. Users rely on the Registry for dependency resolution, and the current latest visible version is v2.6.0. [esp_lvgl_port comp; esp_lvgl_port repo changelog]

Workaround for users (until a new release is published)

• Consume the component directly from the esp-bsp Git repository (pin to a commit or branch) using ESP-IDF’s component manager “git” source method, if your project requires those unreleased fixes. The official steps for pulling from a Git repository are documented in component management; however, the specific git-based manifest snippet isn’t shown in the provided sources. If needed, we can share that once it’s available in the referenced docs. [Component release guide]

If you need us to verify a particular fix from “Unreleased,” please point to the specific commit or behavior and we can double-check whether it’s included in the next publish.