Open question #7 from zen-clock's docs/microlink-registry-migration.md. Low priority — does not block publishing.
idf_component.yml declares idf: ">=6.0,<7.0", but nothing verifies the upper half of that range. The matrix currently covers v6.0.1 and release-v6.0; release-v6.0 is an early warning in the backward direction (does IDF 6.0-generic still work) and says nothing about 6.1.
Until a release-v6.1 cell exists, the <7.0 ceiling is an assumption rather than a tested claim. Add the cell as continue-on-error first so a broken 6.1 does not turn CI red before anyone has looked at it.
Open question #7 from zen-clock's
docs/microlink-registry-migration.md. Low priority — does not block publishing.idf_component.ymldeclaresidf: ">=6.0,<7.0", but nothing verifies the upper half of that range. The matrix currently coversv6.0.1andrelease-v6.0;release-v6.0is an early warning in the backward direction (does IDF 6.0-generic still work) and says nothing about 6.1.Until a
release-v6.1cell exists, the<7.0ceiling is an assumption rather than a tested claim. Add the cell ascontinue-on-errorfirst so a broken 6.1 does not turn CI red before anyone has looked at it.