Pin ESP-IDF to v6.1-beta1 (ride the betas toward v6.1 GA)#40
Merged
Conversation
Moves the pinned ESP-IDF from the rolling release/v6.1 branch commit (v6.1-dev-5215, 2026-06-08) to the tagged v6.1-beta1 pre-release (commit b1d13e9f, 2026-06-24, +168 commits). Riding the tagged betas toward v6.1 GA surfaces any breakage from the v6.1 delta incrementally rather than all at once at the GA re-pin, and gives a fixed, signed pin for both local and CI instead of a moving branch tag. Not yet built or hardware-tested against beta1 — this commit only moves the pin; the ESP32 build + full hardware re-test pass (all variants) runs against the beta1 toolchain before this merges. Known open question: the P4-WiFi boot crash (esp-idf #18759, sleep_clock_icg_startup_init OOM) — the beta1 delta's sleep-retention commits are ESP32-S31-specific, not P4, and pmu_sleep_clock_icg.c is unchanged, so beta1 is unlikely to fix it; a bench try on the P4-NANO confirms either way. Scripts / MoonDeck: - setup_esp_idf.py: PINNED_IDF_COMMIT / PINNED_IDF_VERSION → b1d13e9f / v6.1-beta1; the drift-recovery hint fetches the tag instead of the branch. Docs / CI: - release.yml: the esp-idf-ci-action Docker tag release-v6.1 → v6.1-beta1 (a fixed signed image, so CI and local build the identical tree, not the rolling branch tag); cache key bumped to invalidate. - building.md: the clone commands, the tested-version line, and the § ESP-IDF version rationale updated for the beta1 tag pin and the ride-the-betas-to-GA strategy. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 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 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Moves the pinned ESP-IDF from the rolling
release/v6.1branch commit (v6.1-dev-5215, 2026-06-08) to the taggedv6.1-beta1pre-release (commitb1d13e9f, 2026-06-24, +168 commits). Both local (setup_esp_idf.py) and CI (theesp-idf-ci-actionDocker tag inrelease.yml) move together, so the two build environments stay identical.Why
Ride the tagged betas toward v6.1 GA (targeted late July 2026) rather than jumping straight from the dev branch to GA. This surfaces any breakage from the v6.1 delta incrementally — one beta at a time — instead of all at once at the GA re-pin, and swaps a moving branch tag for a fixed, signed pre-release pin.
Verified locally (macOS, against the real beta1 toolchain)
esp32(classic)esp32p4-eth-wifiesp_hosted+esp_wifi_remotecompile + linkesp32p4-ethruntime (P4-NANO)P4-WiFi boot crash (esp-idf #18759) — still present on beta1
The P4-WiFi variant was flashed to the P4-NANO on beta1 and still bootloops with the known upstream crash, verbatim:
Expected: the beta1 delta's sleep-retention commits are ESP32-S31-specific, and
pmu_sleep_clock_icg.c(the crashing file) is unchanged. TheCONFIG_PM_ENABLE-gating fix #18759 needs has not landed. Soesp32p4-eth-wifistays held out of the release matrix; onlyesp32p4-ethships for the P4. This PR does not change that — it's a build-de-risking pin bump, not a P4-WiFi fix.What CI validates here
release.yml(triggered by this PR touching.github/workflows/release.yml+moondeck/build/**) builds everyships=Truevariant against thev6.1-beta1Docker image — the CI-side confirmation of the local macOS builds above.Notes
docs/building.md § ESP-IDF version).src/changes — this is purely the IDF pin (setup script, CI Docker tag, building.md).🤖 Generated with Claude Code