11215 Commits (6914710977d41571f79e4eef7aefdb3ce4e79595)

 

All Branches   

Search

Author	SHA1	Message	Date
Rich Harris	6914710977	WIP	1 week ago
Rich Harris	9b34d8ff76	tidy up	1 week ago
Rich Harris	1747c7b190	lint	1 week ago
Rich Harris	3dd1d67155	print cv/wv when logging tree	1 week ago
Rich Harris	e4219d5452	WIP	1 week ago
Rich Harris	9e09508df4	WIP	1 week ago
Rich Harris	e39f561ac9	unused	2 weeks ago
Rich Harris	679690b712	DRY	2 weeks ago
Rich Harris	253a20efdd	get rid of batch.wvs	2 weeks ago
Rich Harris	0a0352d289	tweak	2 weeks ago
Rich Harris	3ede5c475c	tweak	2 weeks ago
Rich Harris	cf730f63f8	tweak	2 weeks ago
Rich Harris	6bec42033c	tweak	2 weeks ago
Rich Harris	18da3a361f	prevent double apply	2 weeks ago
Rich Harris	bc32eb369d	no more batch_values	2 weeks ago
Rich Harris	84a8996ee0	WIP	2 weeks ago
Rich Harris	314ad262df	WIP	2 weeks ago
Rich Harris	92642f0150	WIP	2 weeks ago
Rich Harris	9702a307e1	WIP	2 weeks ago
Rich Harris	e95b77cf81	WIP	2 weeks ago
Rich Harris	05688df719	get rid of batch_cvs	2 weeks ago
Rich Harris	8308cb86b6	WIP	2 weeks ago
Rich Harris	ac3afefcde	get rid of batch_wvs	2 weeks ago
Rich Harris	18479217a7	create new active_batch concept	2 weeks ago
Rich Harris	6beb6c6346	redundant	2 weeks ago
Rich Harris	eca510c6bf	unused	2 weeks ago
Rich Harris	ef744bea46	combine previous and previous_wvs	2 weeks ago
Rich Harris	04f773ea0e	WIP	2 weeks ago
Rich Harris	e12ac55b57	i don't think we need this	2 weeks ago
Rich Harris	0c5083ce2b	note to self	2 weeks ago
Rich Harris	e6206ce482	bail out of mark_reactions if wv > cv	2 weeks ago
Rich Harris	71e4901625	avoid allocation	2 weeks ago
Rich Harris	e7fc7f1cea	merge main	2 weeks ago
Rich Harris	a9530e5330	chore: add labels to more internal deriveds (#18050) ... tiny QoL thing	2 weeks ago
Rich Harris	704e3bb5f0	chore: agent hints for perf investigations (#18047) ... This adds some hints in an `AGENTS.md` for how to conduct performance investigations, along with a utility for comparing profiles from different branches to identify hotspots. We will likely want to put other stuff in `AGENTS.md` in future but I figured we could start with something immediately useful. It also tweaks the comparison script — rather than nuking results from existing branches, it keeps them around so that we don't need to re-run benchmarks (which takes a long time) for branches that haven't changed. --------- Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com>	2 weeks ago
Rich Harris	c93e251654	fix: never set derived.v inside fork (#18037) ... This started out as me implementing https://github.com/sveltejs/svelte/pull/17998/changes#r3018047965, but then I realised that I'd also fixed the bug that #17998 addresses. So I guess it's an alternative to that PR --------- Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com>	2 weeks ago
Rich Harris	9cc5a79405	Merge branch 'main' into incremental-batches	2 weeks ago
Rich Harris	345b8ed69f	chore: keep previous benchmark runs around (#18049) ... extracted from #18047 – will self-merge this bit	2 weeks ago
Rich Harris	d00287ca67	Merge branch 'benchmark-markdown' into incremental-batches	2 weeks ago
Rich Harris	ce6e3e3ee7	chore: generate markdown files from CPU profiles for agent-driven investigations	2 weeks ago
Rich Harris	c5377d3e81	apparently unnecessary?	2 weeks ago
Rich Harris	7034256ec3	Merge branch 'main' into incremental-batches	2 weeks ago
Rich Harris	e402b2d0d6	chore: write `pnpm bench:compare` report to disk (#18045) ... will give this a quick self-merge to unblock	2 weeks ago
Rich Harris	f44e5c5d14	Merge branch 'main' into incremental-batches	2 weeks ago
Rich Harris	99b1467ba4	chore: generate CPU profiles when running benchmarks (#18043) ... This causes `pnpm bench` and `pnpm bench:compare` to generate `.cpuprofile` files for each benchmark, which should in theory make it easier to understand how different branches affect performance (and find opportunities for optimisation). These files can be opened directly in VS Code and other editors, or in [profiler.firefox.com](https://profiler.firefox.com), [speedscope.app](https://www.speedscope.app), Chrome's performance devtools and so on.	2 weeks ago
Rich Harris	edcbb0e640	fix: invalidate `@const` tags based on visible references in legacy mode (#18041) ... closes #17992	2 weeks ago
Rich Harris	ff3495dc05	fix: disallow `--` in `idPrefix` (#18038) ... supersedes #17993	2 weeks ago
Scott Wu	51629ec7bd	docs: update references to `vite-plugin-svelte` (#18027) ... ### Before submitting the PR, please make sure you do the following - [ ] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs - [ ] Prefix your PR title with `feat:`, `fix:`, `chore:`, or `docs:`. - [ ] This message body should clearly illustrate what problems it solves. - [ ] Ideally, include a test that fails without this PR but passes with it. - [ ] If this PR changes code within `packages/svelte/src`, add a changeset (`npx changeset`). ### Tests and linting - [ ] Run the tests with `pnpm test` and lint the project with `pnpm lint` --------- Co-authored-by: Rich Harris <hello@rich-harris.dev> Co-authored-by: Rich Harris <rich.harris@vercel.com>	2 weeks ago
dagecko	e0f925116c	fix: pin 9 actions to commit SHA (#18025) ... Re-submission of #18017. Had a problem with my fork and had to delete it, which closed the original PR. Apologies for the noise. ## Summary This PR pins all GitHub Actions to immutable commit SHAs instead of mutable version tags. - Pin 9 unpinned actions to full 40-character SHAs - Add version comments for readability ## Changes by file | File | Changes | |------|---------| | autofix.yml | Pinned actions to SHA | | ci.yml | Pinned actions to SHA | | pkg.pr.new.yml | Pinned actions to SHA | | release.yml | Pinned actions to SHA | ## A note on internal action pinning This PR pins all actions including org-owned ones. Best practice is to pin everything — the tj-actions/changed-files attack was an internally maintained action that was compromised, and every repo referencing it by tag silently executed attacker code. That said, it's your codebase. If you'd prefer to leave org-owned actions unpinned, let us know and we'll adjust the PR. ## How to verify Review the diff — each change is mechanical and preserves workflow behavior: - **SHA pinning**: `action@v3` becomes `action@abc123 # v3` — original version preserved as comment - No workflow logic, triggers, or permissions are modified I wrote a scanner called Runner Guard and open sourced it [here](https://github.com/Vigilant-LLC/runner-guard). If you have any questions, reach out. I'll be monitoring comms. \- Chris Nyhuis (dagecko)	2 weeks ago
Simon H	97d45f85c6	fix: don't override `$destroy/set/on` instance methods in dev mode (#18034) ... Don't think we need a test for this Fixes #17988	2 weeks ago