Skip to content

fix(desktop): hide the offcanvas-collapsed sidebar so it stops painting over the community rail - #5947

Merged
wesbillman merged 1 commit into
mainfrom
wintermute/fix-offcanvas-sidebar-clipping
Aug 15, 2026
Merged

fix(desktop): hide the offcanvas-collapsed sidebar so it stops painting over the community rail#5947
wesbillman merged 1 commit into
mainfrom
wintermute/fix-offcanvas-sidebar-clipping

Conversation

@thomaspblock

@thomaspblock thomaspblock commented Aug 15, 2026

Copy link
Copy Markdown
Contributor

Summary

Collapsing the sidebar left a phantom copy of it painted over the community/relay rail — opaquely on flat themes (vesper et al., which made the rail look removed), and as ghost fragments (muted search-box fill, truncated channel-name tails) on the Buzz themes whose chrome is intentionally transparent for the gradient.

Cause: #4281 made the app-sidebar layer overflow-visible (the huddle drawer needs to escape it). That removed the ancestor clipping the offcanvas collapse relied on: the sidebar slides to left: -sidebar-width but kept painting, exactly over the z-0 rail (z-10 sidebar layer).

Fix: the offcanvas-collapsed sidebar container is now invisible + pointer-events-none, with visibility added to the transition list so the 200 ms slide-out still animates and the flip happens only at the transition's end. Theme-independent; no per-theme CSS touched; the huddle drawer's overflow-visible is preserved.

Before / after

Left 420px of the app with the sidebar collapsed. Before = unpatched origin/main @ 69107dc; after = this branch. Same seeded state, same build pipeline (build:e2e between checkouts).

theme before (ghost sidebar over the rail) after (rail clean: A / B / + visible)
vesper before-vesper after-vesper
buzz before-buzz after-buzz
buzz-dark before-buzz-dark after-buzz-dark

Before shots: ghost ⌘K search chip + blue active-item pill painted over the rail column; on vesper the opaque panel hides the rail buttons entirely. After: the rail's community buttons (A, B) and + are visible and clickable in all three themes.

Reported by Thomas P in #buzz-bugs: buzz://message?channel=e62570dd-33ad-42c5-b92b-75f2689f9694&id=9ea401ca1d009f555ca4324e136f8d8d8156db2f8afa3ff89fd038d2c16260f7

cc @klopez4212 — this touches the layout your #4281/#5478 work shaped; please confirm it doesn't defeat the huddle drawer or glass intentions. The change deliberately hides only the offcanvas-collapsed container, nothing in the expanded path.

Test plan

  • New Playwright regression spec sidebar-offcanvas-rail.spec.ts (buzz / buzz-dark / vesper): collapsed sidebar must be visibility: hidden + pointer-events: none, community rail stays visible and interactive. Fails on unpatched build (verified), passes with the fix.
  • Full desktop unit suite: 4,954 pass / 0 fail
  • pnpm typecheck, pnpm check (biome + file-size ratchet + px-text + pubkey-truncation) green
  • Before/after screenshots above captured via the e2e harness on both builds

…ng over the community rail

The app-sidebar layer became overflow-visible in #4281 (the huddle
drawer needs to escape it), which removed the ancestor clipping the
offcanvas collapse relied on: the "collapsed" sidebar slides to
left: -sidebar-width but kept painting, exactly over the z-0 community
rail. On flat themes (vesper et al.) its opaque bg-sidebar covered the
rail entirely; on the Buzz themes the chrome is transparent for the
gradient, so the rail showed through but sidebar children still painted
as ghosts (the muted search-box fill, truncated channel-name tails).

Make the collapsed offcanvas container invisible and non-interactive,
with `visibility` added to the transition list so the 200ms slide-out
still plays and the flip happens only at the transition's end.

Adds a Playwright regression spec (buzz / buzz-dark / vesper) that
fails on the unpatched build: collapsed sidebar must be
visibility:hidden + pointer-events:none while the community rail stays
visible and interactive.

Reported-in: buzz://message?channel=e62570dd-33ad-42c5-b92b-75f2689f9694&id=9ea401ca1d009f555ca4324e136f8d8d8156db2f8afa3ff89fd038d2c16260f7

Co-authored-by: Thomas Petersen <thomasp@squareup.com>
Signed-off-by: Thomas Petersen <thomasp@squareup.com>
@thomaspblock
thomaspblock requested a review from a team as a code owner August 15, 2026 11:42
@thomaspblock

Copy link
Copy Markdown
Contributor Author

Regenerated before/after proof (previous embeds used relay media URLs, which GitHub's camo proxy rejects — this comment uses the repo's post-screenshots.sh immutable hosting).

Left 420px of the app, sidebar collapsed. Before (unpatched origin/main @ 69107dc): the offcanvas sidebar keeps painting over the community rail — ghost ⌘K search chip and blue active-item pill on the left edge; on vesper the opaque panel wipes the rail entirely. After (this PR): the rail's A / B / + buttons are clean and clickable in all three themes.

vesper

before after
before-vesper after-vesper

buzz

before after
before-buzz after-buzz

buzz-dark

before after
before-buzz-dark after-buzz-dark

thomaspblock pushed a commit that referenced this pull request Aug 15, 2026

@wesbillman wesbillman left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CLEAR at exact head ecfc7fb0c0d058fb402af49e656123b8326c8c2f.

I traced the desktop Sidebar primitive through both consumers (AppSidebar and Settings), the provider state/shortcut path, the community-rail stacking boundary, and the huddle-driven overflow-visible layout. The fix is correctly scoped to desktop collapsible="offcanvas" state: visibility:hidden removes the collapsed subtree from paint, hit testing, keyboard focus, and the accessibility tree; pointer-events:none prevents interception during the 200 ms slide-out before visibility flips. Expanded, icon, non-collapsible, and mobile Sheet paths are unchanged.

The regression runs in the Desktop smoke project across buzz, buzz-dark, and vesper and pins the computed collapsed visibility/pointer-event contract plus rail visibility. One non-blocking test nit: the prose says the rail is interactive, but the test only checks visibility rather than clicking the second community. The computed pointer-events:none assertion directly covers the original interception mechanism, so I do not consider that omission a merge blocker.

Remote PR head matched this clean local review head; git diff --check origin/main...HEAD passed. Exact-head Desktop/E2E/DCO checks are green. No correctness, accessibility, security, privacy, or user-trust finding.

@wesbillman wesbillman left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mongo exact-head review at ecfc7fb0c0d058fb402af49e656123b8326c8c2f: code-clear / merge-ready.

I traced both desktop consumers of the shared Sidebar (AppSidebar and SettingsView), the provider's expanded/collapsed state transition, the overflow-visible app-shell ancestry, left/right and offcanvas/icon variants, and the huddle drawer placement. The change is narrowly scoped to the desktop offcanvas-collapsed sliding container: visibility becomes hidden only at the end of the existing 200 ms transition, visible immediately on expansion, and pointer-events: none prevents the offscreen z-10 layer from intercepting the z-0 community rail. It does not alter mobile Sheet behavior, icon collapse, expanded sidebar rendering, or the separately rendered huddle drawer slot.

The regression covers the three materially different theme surfaces and is in the smoke project. Exact-head Desktop Core/build/smoke/integration checks and DCO are green; git diff --check origin/main...HEAD passes. No correctness, accessibility, breakpoint, animation, or huddle regression blocker found.

Non-blocking test hardening: the spec's fixed waitForTimeout(500) can be removed because toHaveCSS("visibility", "hidden") already polls the actual transition completion. Also, the final “interactive” claim would be stronger if it clicked community B and asserted the active marker rather than only checking visibility. Neither weakens confidence in this production patch because the test directly asserts the offending layer is hidden and has pointer-events: none, and the visual before/after proof reproduces the paint defect.

@wesbillman wesbillman left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Carl, an automated reviewer, commenting via Wes’s GitHub account.

Reviewed the exact head ecfc7fb0c0d058fb402af49e656123b8326c8c2f adversarially across the sidebar state transition, responsive/mobile branch, z-index and overflow ancestry, Huddle drawer boundary, theme behavior, and regression coverage.

No actionable findings. The change is narrowly scoped to the desktop offcanvas-collapsed container: visibility removes its painted and accessibility subtree only after the existing 200 ms exit transition, pointer-events: none prevents the displaced layer from intercepting the community rail, and expanded/icon/mobile paths remain outside the selector. The Huddle drawer remains outside the sidebar container and the overflow-visible shell is preserved.

Independent verification on the clean exact-head worktree:

  • pnpm build:e2e
  • pnpm exec playwright test tests/e2e/sidebar-offcanvas-rail.spec.ts --project=smoke → 3/3 passed (buzz, buzz-dark, vesper)
  • git diff --check 69107dc3bfecbb80cc5f5b8bb6a7647ad054ce57..HEAD

I also confirmed all current GitHub checks for this head are completed successfully or intentionally skipped. I did not approve because Wes did not request an approval review.

@wesbillman
wesbillman merged commit 78cbffe into main Aug 15, 2026
24 checks passed
@wesbillman
wesbillman deleted the wintermute/fix-offcanvas-sidebar-clipping branch August 15, 2026 14:49
RossHartmann added a commit to Kiingo/buzz that referenced this pull request Aug 16, 2026
* Projects v3: unify sharing, discussions, and issue ownership (block#5792)

## Summary

Projects v3 makes repository work shareable, discussion-aware, and
easier to scan in one coherent workspace. People can copy canonical
links, reopen the exact workspace tab, understand issue and pull-request
context at a glance, find related channel conversations, and assign or
unassign issues across Desktop and CLI.

- **Unified workspace** — top-level sections sit above repository
controls in one rounded workspace, with navigation positioned close to
the page heading. README and Files retain branch selection; every
section has a labeled icon header, and Issues and Pull Requests expose
creation from a consistent right-aligned action.
- **Repository management** — the repository selector is always
available, including single-repository projects. Its integrated add flow
lets project owners create a repository manually or select an existing
repository without a separate toolbar button.
- **Readable work-item lists** — issue and pull-request rows use
plain-language context instead of opaque metadata. Files, commits,
issues, pull requests, channels, and contributors share consistent row
density and right-aligned timestamps, while deterministic
fallback-avatar colors keep participants distinct on light backgrounds.
Inbox pull-request metadata wraps between complete phrases and truncates
long channel names instead of compressing copy into narrow columns.
- **Reliable entity links** — projects, repositories, issues, pull
requests, and commits have canonical `buzz://` links, preview cards, OS
deep-link routing, and tab-aware navigation. Reopening the same link
re-applies its destination instead of leaving the user on a locally
selected tab.
- **Related conversations** — repository and work-item views surface
channels discussing the current entity, including participants, channel
navigation, message context, and an explicit notice when discovery
reaches its 500-result cap.
- **Reversible issue ownership** — trusted assignment and unassignment
events work across Desktop, Tauri, `buzz-sdk`, and `buzz issues`.
Assignees appear in project views and the assigned inbox, while
authorized users can remove assignments directly from the assignee row.

Assignment state is derived chronologically from labeled Nostr notes.
Issue authors and repository owners may change any assignee; other users
may only assign or unassign themselves. Shared golden fixtures keep
entity-link grammar and validation aligned across TypeScript and Rust.

The branch also updates `webbrowser` to the patched release for
RUSTSEC-2026-0257.

### Related issue

N/A.

### Testing

- [x] `just ci` — formatting, lint, typechecking, unit tests, and builds
passed
- [x] Full pre-push suite — organization, branch-skew, Desktop checks,
typechecking, and tests passed on the latest push
- [x] `cargo test -p buzz-cli` and focused `buzz-sdk` assignment tests
passed
- [x] Focused Tauri recipient-note and 500-result search-limit tests
passed
- [x] Desktop entity-link and issue-assignment unit tests passed
- [x] Playwright smoke coverage passed for assignment, repeated
entity-link navigation, repository create/select flows, section headers
and actions, timestamp alignment, timeline icons, sentence-style
issue/PR metadata, header spacing, avatar contrast, and Inbox metadata
at stacked and side-rail breakpoints
- [ ] Manual staging pass: link round-trips, Channels tab, assignment
flows, and inbox routing

### Screenshots

Pull requests explain who opened the request, where it lives, and which
branch it comes from; fallback avatars remain visually distinct.

![Pull request list with conversational
metadata](https://raw.githubusercontent.com/block/buzz/2a536de86f7e6f79b349d7bc147b2923ff2b817d/pr-5624--05-pr-list-metadata.png)

Issues use the same sentence-style hierarchy while keeping status and
recency easy to scan.

![Issue list with conversational
metadata](https://raw.githubusercontent.com/block/buzz/2a536de86f7e6f79b349d7bc147b2923ff2b817d/pr-5624--06-issue-list-metadata.png)

The wide Inbox detail keeps author, timestamp, and origin context
readable beside its metadata rail.

![Pull request Inbox detail with readable
metadata](https://raw.githubusercontent.com/block/buzz/e65b433e14b97c45365ed7b68ea402ec01d26615/pr-5624--02-pull-request-detail-wide.png)

[View the complete six-state Projects v3 screenshot
set](block#5624 (comment))
and [the compact/wide Inbox
comparison](block#5624 (comment)).


---

> Supersedes block#5624, whose head commit accumulated permanently-queued
required check suites (block-dco-check et al.) that GitHub never
dispatched. History flattened into a single signed-off commit on latest
main; tree verified byte-identical (`git merge-tree`) to merging the
original branch into main.

---------

Signed-off-by: Thomas Petersen <thomasp@squareup.com>
Co-authored-by: Wintermute <3f1797424fd9ad6653a83665c660517777cd7f8c228c0d5907f49e01537f3ca5@buzz.block.builderlab.xyz>

* fix(desktop): restore the agent trading-card mint button (block#5900)

## Problem

PR block#5574's profile-panel redesign dropped `ProfileSummaryView`'s
`onCreateCard` prop — the only caller of `setCardMintTarget` — so the
entire Agent Trading Cards feature (block#3278) became unreachable from the
GUI while staying fully wired underneath: mint dialog, background job
store, viewer, gallery, composer chip, and the Rust
`mint_agent_card`/`save_agent_card` commands all survive at main. `git
log -S 'setCardMintTarget('` shows exactly two commits: the feature and
the accidental removal.

## Outcome

The mint trigger returns as a management row in the agent profile's Info
tab, directly under **Export agent**, gated `isBot && canManagePersona`
exactly like Duplicate/Export. Target resolution is byte-for-byte the
original logic: prefer the live instance pubkey, fall back to the
persona/definition id, allow locking only when an instance keypair
exists.

## Shape

- `UserProfileAgentManagementRows`: new optional `onCreateCard` row
(Sparkles icon, `user-profile-create-card-row`), placed after Export.
- Prop threaded `UserProfilePanel` → `ProfileSummaryView` →
`ProfileInfoTabContent` → management rows, mirroring `onExportAgent` at
every layer.
- The mint-target state + open callback move into a `useCardMint` hook
in `UserProfilePersonaDialogs` (beside the `CardMintTarget` type it
manages). This keeps `UserProfilePanel.tsx` at 999 lines — the file sits
at the size-ratchet cap and may not grow.

## Validation

- `pnpm check` green (biome, file-size ratchet, px-text,
pubkey-truncation).
- `pnpm typecheck` green.
- Full desktop unit suite: **4888 passed, 0 failed**.
- Profile e2e spec: **32 passed**, including the updated
management-row-order assertion and a new click → mint-dialog-visible →
Escape → closed exercise of the restored row.

Verified at `bff3110a0aeb3d63683eac9ed3e587829f9436da`, one commit atop
main `01f76ec97`.

Signed-off-by: Eva <011987e296fd5006292d2f930b574be47c7801048d1983c46c425d3c95f0cffd@buzz.block.builderlab.xyz>
Co-authored-by: Eva <011987e296fd5006292d2f930b574be47c7801048d1983c46c425d3c95f0cffd@buzz.block.builderlab.xyz>

* fix(ci): read Playwright version without nested shell quoting (block#5910)

## Summary

- replace the nested one-line shell quoting used to read the Playwright
package version
- write the resolved version to `GITHUB_OUTPUT` from a multiline shell
step

## Why

The `desktop-v0.5.12` release smoke job failed before executing tests
because Bash received escaped quotes inside command substitution and
parsed the Node expression as shell syntax.

## Validation

- `bash scripts/test-release-ref-contract.sh`
- isolated execution of the new shell fragment with a fixture
`@playwright/test/package.json`, producing `version=1.58.2`
- `git diff --check`

Signed-off-by: Wes <wesbillman@users.noreply.github.com>
Co-authored-by: Carl <c7ebe626f000404285d3686e1dc74cc07cc60a9754a150041ba132e14bd3e2ec@buzz.block.builderlab.xyz>

* chore(release): release Buzz Desktop version 0.5.13 (block#5912)

## Buzz Desktop release v0.5.13

- **Frozen main:** `09768100ec3420f0aa7cd278bd00fe0baab5de8d`
- **Reviewed candidate:** `a239e0f6793ac6e88ccf92cc231054090a9753cc`
- **Previous desktop release:** `desktop-v0.5.12`
- **Proposed immutable tag:** `desktop-v0.5.13`

This PR may be **squash merged** after the Desktop Release Candidate
check and all protected-branch checks pass. Merging authorizes
publication of the exact reviewed candidate; later or unrelated changes
on `main` cannot alter it.

The checked-in changelog accounts for every non-merge commit in the
release range. The Desktop tag points to the reviewed candidate commit,
not the later squash commit. Publication remains bound to that immutable
candidate tag.

Signed-off-by: Wes <wesbillman@users.noreply.github.com>
Co-authored-by: Release Automation <release-automation@users.noreply.github.com>

* ci(release): remove desktop smoke gate (block#5914)

## Summary

- remove the GitHub-hosted desktop smoke job from the desktop release
workflow
- remove the smoke result from manifest assembly dependencies and
promotion conditions
- retain the local smoke tooling for future repair and targeted
validation

The first release execution of this gate spent its full 10-minute
Playwright timeout traversing the 10,000-row fixture, then produced a
987 MB diagnostics upload. All signed platform builds succeeded, but the
smoke prevented manifest publication. This restores the previously
established release boundary while the harness is made suitable for CI
separately.

### Testing

- parsed `.github/workflows/release.yml` with Ruby Psych and asserted
the smoke job/dependencies are absent
- `scripts/test-release-ref-contract.sh`
- exact pushed commit passed the repository pre-push hook

Signed-off-by: Wes <wesbillman@users.noreply.github.com>
Co-authored-by: Carl <c7ebe626f000404285d3686e1dc74cc07cc60a9754a150041ba132e14bd3e2ec@buzz.block.builderlab.xyz>

* chore(release): release Buzz Desktop version 0.5.14 (block#5917)

## Buzz Desktop release v0.5.14

- **Frozen main:** `1b3dbcaaea882eeea90359c1db02e306d2f4f50a`
- **Reviewed candidate:** `391495e7d347d20b67e39e3c240d17ef63c5c2c0`
- **Previous desktop release:** `desktop-v0.5.13`
- **Proposed immutable tag:** `desktop-v0.5.14`

This PR may be **squash merged** after the Desktop Release Candidate
check and all protected-branch checks pass. Merging authorizes
publication of the exact reviewed candidate; later or unrelated changes
on `main` cannot alter it.

The checked-in changelog accounts for every non-merge commit in the
release range. The Desktop tag points to the reviewed candidate commit,
not the later squash commit. Publication remains bound to that immutable
candidate tag.

Signed-off-by: Wes <wesbillman@users.noreply.github.com>
Co-authored-by: Release Automation <release-automation@users.noreply.github.com>

* Polish mobile message threads and composer (block#5645)

## Summary

- refine mobile message metadata, search spacing, and Activity filter
semantics
- add channel-parity Latest navigation and stable tail following to
threads
- synchronize Android composer/keyboard geometry and keep Latest spacing
stable across IME transitions

## Validation

- `bin/just mobile-check`
- `bin/just mobile-test` (1,276 tests)
- Pixel 10 install/launch and channel/thread keyboard, Latest, tail, and
back-navigation review
- signed iPhone install/launch workflow

## Snapshots

See the review snapshots below.

---------

Signed-off-by: kenny lopez <klopez4212@gmail.com>
Signed-off-by: Kenny Lopez <klopez4212@gmail.com>
Signed-off-by: Princess Donut <b238ea756dee4d98afa5883fc7f1de61eeabe65bf700e3a5a5a80db5e42e2c2b@buzz.block.builderlab.xyz>
Co-authored-by: Fast Fizz <2df81cb51f05a9d5387ef24d7b9ecb8fcdfcd1c70ffabc67061c9596e1b5b1c4@buzz.block.builderlab.xyz>
Co-authored-by: Princess Donut <b238ea756dee4d98afa5883fc7f1de61eeabe65bf700e3a5a5a80db5e42e2c2b@buzz.block.builderlab.xyz>

* fix(desktop): hide the offcanvas-collapsed sidebar so it stops painting over the community rail (block#5947)

## Summary

Collapsing the sidebar left a phantom copy of it painted over the
community/relay rail — opaquely on flat themes (vesper et al., which
made the rail look *removed*), and as ghost fragments (muted search-box
fill, truncated channel-name tails) on the Buzz themes whose chrome is
intentionally transparent for the gradient.

**Cause:** block#4281 made the app-sidebar layer `overflow-visible` (the
huddle drawer needs to escape it). That removed the ancestor clipping
the offcanvas collapse relied on: the sidebar slides to `left:
-sidebar-width` but kept painting, exactly over the `z-0` rail (`z-10`
sidebar layer).

**Fix:** the offcanvas-collapsed sidebar container is now `invisible` +
`pointer-events-none`, with `visibility` added to the transition list so
the 200 ms slide-out still animates and the flip happens only at the
transition's end. Theme-independent; no per-theme CSS touched; the
huddle drawer's `overflow-visible` is preserved.

## Before / after

Left 420px of the app with the sidebar collapsed. Before = unpatched
`origin/main` @ 69107dc; after = this branch. Same seeded state, same
build pipeline (`build:e2e` between checkouts).

| theme | before (ghost sidebar over the rail) | after (rail clean: A /
B / + visible) |
|---|---|---|
| vesper |
![before-vesper](https://raw.githubusercontent.com/block/buzz/3f98c576e062e51d976940725d84b4e0be7fd53c/pr-5947--before-vesper.png)
|
![after-vesper](https://raw.githubusercontent.com/block/buzz/3f98c576e062e51d976940725d84b4e0be7fd53c/pr-5947--after-vesper.png)
|
| buzz |
![before-buzz](https://raw.githubusercontent.com/block/buzz/3f98c576e062e51d976940725d84b4e0be7fd53c/pr-5947--before-buzz.png)
|
![after-buzz](https://raw.githubusercontent.com/block/buzz/3f98c576e062e51d976940725d84b4e0be7fd53c/pr-5947--after-buzz.png)
|
| buzz-dark |
![before-buzz-dark](https://raw.githubusercontent.com/block/buzz/3f98c576e062e51d976940725d84b4e0be7fd53c/pr-5947--before-buzz-dark.png)
|
![after-buzz-dark](https://raw.githubusercontent.com/block/buzz/3f98c576e062e51d976940725d84b4e0be7fd53c/pr-5947--after-buzz-dark.png)
|

Before shots: ghost `⌘K` search chip + blue active-item pill painted
over the rail column; on vesper the opaque panel hides the rail buttons
entirely. After: the rail's community buttons (A, B) and `+` are visible
and clickable in all three themes.

Reported by Thomas P in #buzz-bugs:
buzz://message?channel=e62570dd-33ad-42c5-b92b-75f2689f9694&id=9ea401ca1d009f555ca4324e136f8d8d8156db2f8afa3ff89fd038d2c16260f7

cc @klopez4212 — this touches the layout your block#4281/block#5478 work shaped;
please confirm it doesn't defeat the huddle drawer or glass intentions.
The change deliberately hides only the *offcanvas-collapsed* container,
nothing in the expanded path.

## Test plan

- [x] New Playwright regression spec `sidebar-offcanvas-rail.spec.ts`
(buzz / buzz-dark / vesper): collapsed sidebar must be `visibility:
hidden` + `pointer-events: none`, community rail stays visible and
interactive. **Fails on unpatched build** (verified), passes with the
fix.
- [x] Full desktop unit suite: 4,954 pass / 0 fail
- [x] `pnpm typecheck`, `pnpm check` (biome + file-size ratchet +
px-text + pubkey-truncation) green
- [x] Before/after screenshots above captured via the e2e harness on
both builds

Signed-off-by: Thomas Petersen <thomasp@squareup.com>
Co-authored-by: Wintermute <165f0c871dd2586bb18b6aa109eeaf57bb2132ff4d27b10120f4368a0f627022@buzz.block.builderlab.xyz>

* ci: refresh Buzz 0.5.14 fork baseline

Signed-off-by: Ross Hartmann <1750494+RossHartmann@users.noreply.github.com>

* fix(acp): preserve same-turn action ordering

Signed-off-by: Ross Hartmann <1750494+RossHartmann@users.noreply.github.com>

---------

Signed-off-by: Thomas Petersen <thomasp@squareup.com>
Signed-off-by: Eva <011987e296fd5006292d2f930b574be47c7801048d1983c46c425d3c95f0cffd@buzz.block.builderlab.xyz>
Signed-off-by: Wes <wesbillman@users.noreply.github.com>
Signed-off-by: kenny lopez <klopez4212@gmail.com>
Signed-off-by: Kenny Lopez <klopez4212@gmail.com>
Signed-off-by: Princess Donut <b238ea756dee4d98afa5883fc7f1de61eeabe65bf700e3a5a5a80db5e42e2c2b@buzz.block.builderlab.xyz>
Signed-off-by: Ross Hartmann <1750494+RossHartmann@users.noreply.github.com>
Co-authored-by: thomaspblock <thomasp@squareup.com>
Co-authored-by: Wintermute <3f1797424fd9ad6653a83665c660517777cd7f8c228c0d5907f49e01537f3ca5@buzz.block.builderlab.xyz>
Co-authored-by: Tyler <109685178+tlongwell-block@users.noreply.github.com>
Co-authored-by: Eva <011987e296fd5006292d2f930b574be47c7801048d1983c46c425d3c95f0cffd@buzz.block.builderlab.xyz>
Co-authored-by: Wes <wesbillman@users.noreply.github.com>
Co-authored-by: Carl <c7ebe626f000404285d3686e1dc74cc07cc60a9754a150041ba132e14bd3e2ec@buzz.block.builderlab.xyz>
Co-authored-by: Release Automation <release-automation@users.noreply.github.com>
Co-authored-by: klopez4212 <klopez4212@gmail.com>
Co-authored-by: Fast Fizz <2df81cb51f05a9d5387ef24d7b9ecb8fcdfcd1c70ffabc67061c9596e1b5b1c4@buzz.block.builderlab.xyz>
Co-authored-by: Princess Donut <b238ea756dee4d98afa5883fc7f1de61eeabe65bf700e3a5a5a80db5e42e2c2b@buzz.block.builderlab.xyz>
Co-authored-by: Wintermute <165f0c871dd2586bb18b6aa109eeaf57bb2132ff4d27b10120f4368a0f627022@buzz.block.builderlab.xyz>
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