All status pages · Unowned issues across all projects · How to write a weekly status report from GitHub

Weekly status: sveltejs/svelte

2026-10-14 to 2026-10-20 (7 full days, UTC). Unofficial: generated from this repository’s public GitHub activity by pilotless status. Not affiliated with the project, and no information here that GitHub does not publish.

8 commits to main by 4 people, 13 pull requests merged, 100 open pull requests, 34 open issues on this page of results.

Stalled pull requests

Open, and untouched for seven days or more:

#8975 fix: define role="application" as an interactive ARIA role - last touched 1079 days ago
#14083 docs: update store documentation - last touched 713 days ago
#14116 fix: reset title element to previous value on removal - last touched 669 days ago
#14796 feat: enable animate: directive for snippets - last touched 662 days ago
#14599 Fix: Patch structuredClone to error on $state proxies - last touched 601 days ago

Issues nobody has picked up

Open, unassigned, and with no replies yet:

#19038 Hydrated <input value={...}> loses typed text the first time its template effect re-runs - opened 2 days ago
#19032 Writing state inside an effect costs time exponential in the depth of shared deriveds down - opened 3 days ago
#19016 SSR: onDestroy doesn’t run for components rendered in a discarded bind: re-render pass - opened 5 days ago
#18993 Async hydration reads stale pre-mount writes and removes the component tree - opened 7 days ago
#18986 HTML in option elements cause hydration markers that fail W3C validation (bogus comment) - opened 8 days ago

The two lists above are what a status meeting is usually for. Nobody had to attend one to produce this page.

If you maintain sveltejs/svelte and would rather this page did not exist, open an issue and it will be deleted - no argument, no reply needed beyond the repository name.

Want this for your own repositories? Install the pilotless GitHub App — one click, then a pinned weekly status digest in each selected repo. Prefer CI-only? The status-action is still two lines of YAML with no account and nothing leaving GitHub.