Skip to content

Merge release/10.0.0 into main - #40

Merged
holmesworcester merged 5 commits into
mainfrom
merge/10.0.0-into-main
Sep 16, 2026
Merged

holmesworcester merged 5 commits into
mainfrom
merge/10.0.0-into-main

Conversation

@holmesworcester

Copy link
Copy Markdown

Merges release/10.0.0 back into main.

This one is clean. No conflicts, nothing to reconcile, no hand-built merge. #36 merged
release/9.0.0 into main as a real two-parent merge, so git's merge base here is
742ea3d — release/9.0.0's tip — which is honest. main carries nothing of its own
beyond that release, so git merge produces exactly the release/10.0.0 tree on its own.

9f54efe  parents=[f09a50c 4660383]  Merge release/10.0.0 into main

Three commits come across:

  • b59a210 — disable removal and key rotation in protocol 4
  • 6f534c89 — retain admission and key delivery checks under that removal gate (this is the
    commit Quiet 10.0.0 and QSS 3.0.0 both pin)
  • 4660383 — PR Disable removal and key rotation for Quiet protocol 4 #37, fix/9.1-disable-removal-rotation

43 files, +839/−210, mostly packages/auth/src/team and its tests, including the new
removalRotationGate.test.ts.

Still worth merging with a merge commit rather than squashing

Not a problem here — it's a request for next time. Squashing this would drop the ancestry link
to release/10.0.0 and leave the next release merge computing a stale base. That is exactly
what happened in quiet-storage-service (see TryQuiet/quiet-storage-service#61, which had to be
built by hand against 2.0.2) and in the Quiet client (TryQuiet/quiet#3551). Keeping #36's
two-parent pattern is what has kept this repo easy.

🤖 Generated with Claude Code

holmes and others added 4 commits September 10, 2026 12:30
Disable removal and key rotation for Quiet protocol 4
Brings the 10.0.0 release line back into main: the protocol 4 removal and key
rotation gate (b59a210), the admission and key delivery checks retained under
that gate (6f534c8, the commit Quiet 10.0.0 pins), and PR #37.

No conflicts and nothing to reconcile. #36 merged release/9.0.0 into main as a
real two-parent merge, so git's merge base here is 742ea3d - release/9.0.0's
tip - which is honest. main carries nothing of its own beyond that release, so
the result is exactly the release/10.0.0 tree.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Brings the fixed tests workflow into this PR's merge ref so the Tests check runs with node 20 + pnpm 10.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@holmesworcester
holmesworcester merged commit 1e68ea7 into main Sep 16, 2026
1 check passed
@holmesworcester
holmesworcester deleted the merge/10.0.0-into-main branch September 16, 2026 18:47
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