Skip to content
This repository was archived by the owner on Oct 30, 2026. It is now read-only.

CI: build the CircuitPython leg on CircuitPython 11.0.0-alpha.1 - #32

Merged
bdbarnett merged 1 commit into
mainfrom
ci-circuitpython-11
Oct 9, 2026
Merged

bdbarnett merged 1 commit into
mainfrom
ci-circuitpython-11

Conversation

@bdbarnett

Copy link
Copy Markdown
Contributor

The Linux integration workflow's CircuitPython leg, which release.yml also runs before it publishes, built against CircuitPython 10.3.0 through lvgl-circuitpython's apply_cp_patches.sh. So a change for CircuitPython 11 (like #29) was never built on CircuitPython 11 by CI.

This moves the leg to CircuitPython 11.0.0-alpha.1 and lvgl-circuitpython 46686eb, and builds it the way lvgl-circuitpython's README does: the consumer directory goes to the unix port's make as USER_C_MODULES, with no patches to CircuitPython's tree. The consumer's micropython.mk picks up the bindings under test as its sibling, and refuses them unless they match LVGL_BINDINGS_COMMIT, which the workflow already sets to the checkout under test.

The MicroPython and CPython legs are unchanged.

…user C module

The CircuitPython leg of the Linux integration workflow, which the release
workflow also runs, built against CircuitPython 10.3.0 through
lvgl-circuitpython's patch script, so nothing gated the bindings on
CircuitPython 11. It now checks out 11.0.0-alpha.1 and lvgl-circuitpython
46686eb, and hands lvgl-circuitpython to the unix port's make as
USER_C_MODULES, the way lvgl-circuitpython's README builds it.
@bdbarnett
bdbarnett merged commit 98a5f2f into main Oct 9, 2026
4 checks passed
@bdbarnett
bdbarnett deleted the ci-circuitpython-11 branch October 9, 2026 14:15
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant