Skip to content

Release branch 2026-11-17 - #880

Closed
itz4blitz wants to merge 11 commits into
mainfrom
release/2026-11-17
Closed

itz4blitz wants to merge 11 commits into
mainfrom
release/2026-11-17

Conversation

@itz4blitz

Copy link
Copy Markdown
Collaborator

Summary

Daily release branch for 2026-11-17. Accumulates open queue pull requests that merge cleanly onto current main.

Merged into this branch

Skipped / conflicts

  • PR 836: red checks and not mergeable
  • PR 262: conflict merging into release/2026-11-17
  • PR 825: conflict merging into release/2026-11-17
  • PR 822: conflict merging into release/2026-11-17
  • PR 823: conflict merging into release/2026-11-17
  • PR 824: conflict merging into release/2026-11-17
  • PR 827: conflict merging into release/2026-11-17
  • PR 831: conflict merging into release/2026-11-17
  • PR 832: conflict merging into release/2026-11-17
  • PR 830: conflict merging into release/2026-11-17
  • PR 828: conflict merging into release/2026-11-17
  • PR 829: conflict merging into release/2026-11-17
  • PR 814: conflict merging into release/2026-11-17
  • PR 816: conflict merging into release/2026-11-17
  • PR 813: conflict merging into release/2026-11-17
  • PR 879: conflict merging into release/2026-11-17
  • PR 810: conflict merging into release/2026-11-17
  • PR 820: conflict merging into release/2026-11-17
  • PR 821: conflict merging into release/2026-11-17
  • PR 819: conflict merging into release/2026-11-17
  • PR 817: conflict merging into release/2026-11-17
  • PR 818: conflict merging into release/2026-11-17
  • PR 833: conflict merging into release/2026-11-17
  • PR 862: conflict merging into release/2026-11-17
  • PR 863: conflict merging into release/2026-11-17
  • PR 858: conflict merging into release/2026-11-17
  • PR 851: conflict merging into release/2026-11-17
  • PR 856: conflict merging into release/2026-11-17
  • PR 868: conflict merging into release/2026-11-17
  • PR 876: conflict merging into release/2026-11-17
  • PR 878: conflict merging into release/2026-11-17
  • PR 875: conflict merging into release/2026-11-17
  • PR 870: conflict merging into release/2026-11-17
  • PR 871: conflict merging into release/2026-11-17
  • PR 837: conflict merging into release/2026-11-17
  • PR 838: conflict merging into release/2026-11-17
  • PR 834: conflict merging into release/2026-11-17
  • PR 835: conflict merging into release/2026-11-17
  • PR 842: conflict merging into release/2026-11-17
  • PR 847: conflict merging into release/2026-11-17
  • PR 848: conflict merging into release/2026-11-17
  • PR 845: conflict merging into release/2026-11-17
  • PR 843: conflict merging into release/2026-11-17
  • PR 844: conflict merging into release/2026-11-17

Test plan

  • CI green on this branch
  • Spot-check adapters touched
  • Squash or merge to main when ready, then cut with packaging/release-cut.sh

unRekable and others added 11 commits November 14, 2026 15:18
…t route the server refuses, and the test expects it sealed with an echo that lands (red)
…folds rebuilt in the server's order, owed reactions applied when their message lands, and a reaction that cannot open yet is folded again
…ursor and owed pairs are kept sealed beside the cache, a blob that cannot open yet holds the cursor until it opens or its tries run out, and a restart neither refolds history nor loses a count
`_proof/` and `target-wt/` are ship-it evidence and local build output. They were showing up as untracked work on every checkout.
Opcode 12 names the size, frame rate and bitrate of the share, and is sent again when that quality changes. The picture drive asks for that bitrate. A camera stays one layer.

Closes #338
@github-actions

github-actions Bot commented Nov 17, 2026 •

Copy link
Copy Markdown

Tiny Code Review

⚠️ Code review unavailable · run

the AI provider rate-limited the request

This is advice, not a gate. Re-run with the agent:review label or a /review comment.

@itz4blitz

Copy link
Copy Markdown
Collaborator Author

origin/main is 144ee7c, tagged v0.2.81. It already has #810, #844, and #845. This branch is four commits behind that, and it still has three pulls that are not on main. Do not merge this branch as the release.

Cherry-pick onto origin/main. Skip the merge commits on this branch (0758175, e0ed66e, aa8d4a7).

The same commits are still the heads of the open pulls #264, #860, and #259.

@itz4blitz

Copy link
Copy Markdown
Collaborator Author

Status check: main already has #810, #844, #845 and v0.2.81. The unique commits still waiting to land are #264 and #860, plus #259 (still open, changes requested). Leaving this open until those land.

@itz4blitz

Copy link
Copy Markdown
Collaborator Author

Superseded by and merged in #903 (d387971 — Release 2026-11-20 combined PR).

@itz4blitz itz4blitz closed this Nov 21, 2026
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.

2 participants