Sync layered-env gitlinks with current component mains

Browse Source

Why: Backend, frontend, and documents each gained one commit on main after this branch was cut. The feature commits have to contain those mains so the pull requests can merge.
Evidence: git merge origin/main in each submodule completed with the ort strategy and no conflicts.
Impact: Gitlinks move to the merge commits. The layered environment changes themselves are unchanged.
Refs: .task/feature-layered-python-env.md
Co-authored-by: Cursor <cursoragent@cursor.com>

...

This commit is contained in:

weichen

2026-10-15 14:01:33 +00:00

co-authored by Cursor

parent 3d6de0c4ac

commit f88cc7fb37

3 changed files with 3 additions and 3 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

modules/backend

+1 -1

Submodule modules/backend updated: b85a1e1ca3...9a54845d40

modules/documents

+1 -1

Submodule modules/documents updated: 945db355fc...73bbb4cea6

modules/frontend

+1 -1

Submodule modules/frontend updated: e33d17e1a6...781cde6667