Skip to content

Merge main into feat/054-connector-boundary - #297

Merged
lxsaah merged 2 commits into
feat/054-connector-boundaryfrom
feat/054-merge-main
Oct 6, 2026
Merged

lxsaah merged 2 commits into
feat/054-connector-boundaryfrom
feat/054-merge-main

Conversation

@lxsaah

@lxsaah lxsaah commented Oct 6, 2026

Copy link
Copy Markdown
Contributor

Unblocks #296, which conflicts with main.

#295 brought main (#284, Maximum Packet Size in the embedded CONNECT) into the feature branch. Squash-merging it turned that merge into ordinary changes, so git does not see #284 as merged and #296 conflicts in session_loop.rs and tokio_broker.rs.

This PR records the merge again. The resolution keeps the feature branch's side, so no file changes: the tree is identical to feat/054-connector-boundary.

Please merge this with "Create a merge commit", not squash. A squash would drop the main parent again and #296 would stay conflicting.

🤖 Generated with Claude Code

lxsaah and others added 2 commits October 4, 2026 21:08
Records #284 (Maximum Packet Size in the embedded CONNECT) as merged. Its
content already reached the feature branch through #295, whose squash
dropped the merge parent, so #296 conflicts with main. The resolution
keeps the feature branch's side; the tree is unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@lxsaah
lxsaah merged commit a1c02ba into feat/054-connector-boundary Oct 6, 2026
2 checks passed
@lxsaah
lxsaah deleted the feat/054-merge-main branch October 6, 2026 04:45
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