Skip to content

cloud workspace: clone MicroPython at micropython-pydevices' pinned commit - #112

Merged
bdbarnett merged 1 commit into
mainfrom
dependencies-lock
Nov 10, 2026
Merged

bdbarnett merged 1 commit into
mainfrom
dependencies-lock

Conversation

@bdbarnett

Copy link
Copy Markdown
Contributor

The cloud workspace installer clones MicroPython at the commit micropython-pydevices pins. That pin is a full 40-character commit, and git clone --branch takes only branches and tags, so the clone failed. A full commit is now fetched on its own at depth 1; a tag or branch still goes through clone --branch. The pin is read from micropython-pydevices' DEPENDENCIES.lock, which is replacing UPSTREAM, modules.lock and deps.lock there, and from UPSTREAM in a checkout from before that; PYDEVICES_MP_TAG still overrides both.

ulab's row in data/stack.json pointed at micropython-pydevices' modules.lock, which goes away with that change, and the stack check fails on a path that's gone. It now points at docs/reference/modules.md, which says where ulab comes from and exists before and after. The row's link on the page is ulab's upstream repository either way.

I ran the installer's mp_pin and shallow_clone_if_missing on their own: against a checkout with DEPENDENCIES.lock, one with only UPSTREAM, and none, they print the same commit, the same commit and v1.29.0, and the commit clone lands at that commit. stack.py --check --stale reports 159 rows and no problems. The whole installer wasn't run in a cloud container.

…ommit

micropython-pydevices pins MicroPython by full commit, which clone
--branch can't take, so the interpreter checkout failed. A commit is now
fetched on its own. The pin is read from DEPENDENCIES.lock, where
micropython-pydevices is moving it, or UPSTREAM before that.

ulab's stack row points at micropython-pydevices' modules page, which
exists before and after the move, in place of modules.lock.
@bdbarnett
bdbarnett merged commit 27d3901 into main Nov 10, 2026
9 checks passed
@bdbarnett
bdbarnett deleted the dependencies-lock branch November 10, 2026 16:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant