Skip to content

spork issue tracker #533

@cwillisf

Description

@cwillisf

Several issues have popped up after the recent Scratch editor release, which includes the "spork" (Blockly unforking) work in scratch-blocks. This is a meta-issue to track them. We should file individual issues for each at some point, but that's probably after the most urgent items are hotfixed.

Big thanks to @redspacecat, @nimeratus, @mxmou, @Joeclinton1, @npxl32, and others for collecting reports and contributing technical analysis. See the comments on this issue for the running feed. There is also a community-maintained list at https://scratch.mit.edu/discuss/post/9109627/

Status (2026-04-30): two waves of fixes deployed (2026-04-21 and 2026-04-29). Backpack/broadcast de/serialization fixes (#554 + #555) merged today into the hotfix branch — not yet deployed to production. One community PR still open: #3571 (hat block delete preserves stack), CI clean, awaiting review. Custom block input deletion cursed inputs and the related "potato block" reports are the next fix priority.


P0 -- Data loss / code deletion

P1 -- Silent wrong behavior / runtime failures / interaction failures

P2 -- Blocks editing broken

P3 -- Visual / cosmetic regressions

P4 -- Performance / viewport

P5 -- Low-confidence / adjacent / unreproduced

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions