Skip to content

chore: pin merged Lotus Next actor UI source (#295) - #296

Merged
bigduu merged 1 commit into
mainfrom
zenith-root/chore/295-lotus-actor-ui-source
Sep 28, 2026
Merged

bigduu merged 1 commit into
mainfrom
zenith-root/chore/295-lotus-actor-ui-source

Conversation

@bigduu

@bigduu bigduu commented Sep 28, 2026

Copy link
Copy Markdown
Owner

Summary

Pin the merged Lotus Next actor UI source chain in the Zenith wrapper. This is a source-pointer update only; it does not publish or adopt a new frontend artifact and does not claim live Bamboo integration or completion of the related partial UI Issues.

  • Zenith base: main at 30d21eccc3533717f8d0afe4ab3da1f9e559cd95.
  • PR head: a99f74b8d9573a52e63acf1201a3d073e939c70d.
  • Lotus Next target: merged remote main at cdc226031079063b517fbf862037f7dac4aaad83.

Submodule Updates

Test Plan

  • Verified exact Lotus Next remote main SHA and old-pointer ancestry (ahead_by=80, behind_by=0).
  • Verified git ls-tree before/after and git diff --raw / git diff --name-only: only the lotus-next mode-160000 entry changed.
  • git diff --check HEAD^ HEAD passed; worktree clean.
  • Zenith Submodule Guard must pass on this exact PR head before merge. Local independent pointer review is complete; no GitHub review is requested.

Release boundary

Zenith's committed release configuration still locks @bigduu/lotus-next@2026.9.22 to source a480e2bb94f5dd08fe4b01b2f8844a2c9ed03245. This PR leaves that configuration, Bamboo and Bodhi pointers unchanged. A later immutable artifact and consumer acceptance must reconcile the release snapshot before a release is claimed.

Screenshots

Not applicable: this PR only changes a Git submodule pointer.

Refs #295
Refs bigduu/Bamboo-agent#791

@bigduu
bigduu marked this pull request as ready for review September 28, 2026 02:37
@bigduu
bigduu merged commit 7ee3e22 into main Sep 28, 2026
2 checks passed
@bigduu
bigduu deleted the zenith-root/chore/295-lotus-actor-ui-source branch September 28, 2026 02:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant