chore(deps): update dependency styled-components to ^6.5.1

[squiggler-app]

This PR contains the following updates:

Package	Change	Age	Confidence
styled-components (source)	^6.4.4 → ^6.5.1

---

Release Notes

styled-components/styled-components (styled-components)

v6.5.1

Compare Source

Patch Changes

• a0a92cd: Fix a styled component silently dropping props declared as a union whose members have no prop in common, which left every one of those props rejected. The same applied when as pointed at a component with such props. Where every member's props are optional the union is still flattened, so declare the combined optional shape instead.
• a0a92cd: Styled components now report the same debug value to React DevTools on every render. Previously the value was only reported on renders that recomputed styles, so it disappeared from the DevTools panel whenever a component re-rendered with unchanged style props.
• a0a92cd: Fix wrapping a component whose props are a union. Since 6.5.0 the wrapped version accepted only the props common to every member of the union, so a prop belonging to just one member was rejected even though the unwrapped component accepted it.

v6.5.0

Compare Source

Minor Changes

• dfe4baf: React Native components now check style against React Native's own style types. Web-only CSS such as float, and CSS custom properties such as --brand, were previously accepted even though React Native has never done anything with them at runtime. They now surface as a type error where you write them instead of silently doing nothing.

  const Card = styled.View``;
  
  <Card style={{ padding: 16 }} />; // unchanged
  <Card style={{ float: 'left' }} />; // now a type error

  Web components are unaffected and still accept custom properties.

• dfe4baf: Declaring your own style prop type now constrains the fields you name while leaving the rest of CSS alone. Previously a declaration like styled.div<{ style?: { width: number } }> was quietly ignored, because the built-in style type was applied after your props, so any CSS value was still accepted. Now width has to be a number, while color, custom properties, and everything else you did not mention keep working as before.

  To remove a field rather than constrain it, declare it as never. To make your type the only thing accepted, wrap it in the new CustomStyle helper, which removes every field you did not list:

  const Box = styled.div<{ style?: CustomStyle<{ width: number }> }>``;

  The constraint holds when the component is rendered through as or forwardedAs, so it cannot be sidestepped by rendering the same component as a different tag. Note that CustomStyle removes CSS custom properties too, since they are among the fields you did not list.

  One thing to know if you use exactOptionalPropertyTypes: on a component that declares its own style, passing style={undefined} explicitly is now rejected. Leaving the prop off is unaffected. Write style?: { width: number } | undefined in your declaration if you need to pass it explicitly.

  Relatedly, reading the style type back off a component (for example with React.ComponentProps) now reports that CSS custom properties are accepted, which matches what was already allowed when rendering.

• 2949923: Large TypeScript projects type-check dramatically faster. On a 500-component app, tsc check time drops to under a quarter of what 6.4.4 takes and peak memory to under a third, which resolves the out-of-memory failures some projects hit after upgrading past 6.4.2. Both are now better than 6.4.2 was, so there is no longer a reason to pin to it. Editor responsiveness improves by the same margin, and autocomplete on as targets is unchanged.

Patch Changes

• dfe4baf: Fixed ref being rejected on React Native components created with the shorthand syntax, such as styled.TextInput. Passing a ref, or a ref callback whose parameter you have not annotated, now works the same way it does with styled(TextInput).

  Also fixed a type error when a component's attrs callback is given an explicit parameter type, as in styled.div.attrs<MyProps>(props => props).

• dfe4baf: Fixed components built on targets whose props cannot be inspected, such as Mantine's polymorphic components, rejecting children and the target's own props once you added a prop of your own:

  const Styled = styled(MantineButton)<{ $variant: 'a' | 'b' }>``;
  
  <Styled $variant="a" variant="filled">
    this now works
  </Styled>;

  Wrapping such a target without adding props already worked; adding one turned the permissiveness off. Your own declared props stay strictly typed either way.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "every weekday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate using a curated preset maintained by . View repository job log here

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
auth-test-studio	Ready	Preview	Aug 10, 2026 3:51pm
page-building-studio	Ready	Preview	Aug 10, 2026 3:51pm
studio-metrics	Ready	Preview	Aug 10, 2026 3:51pm
test-studio	Ready	Preview	Aug 10, 2026 3:51pm
test-studio-preview-iframe	Ready	Preview	Aug 10, 2026 3:51pm

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 048ec1a. Configure here.}

[github-actions]

❌ E2E Tests

🟢 111 passed • 🔴 26 failed • 🟡 65 flaky • (⚪ 104 skipped) • view full report • view run

Debug failing tests locally

SANITY_E2E_PROJECT_ID=ittbm412 \
SANITY_E2E_BASE_URL=https://e2e-studio-4eado1d17.sanity.dev \
SANITY_E2E_DATASET=pr-13916-chromium-31405661782 \
SANITY_E2E_DATASET_CHROMIUM=pr-13916-chromium-31405661782 \
SANITY_E2E_DATASET_FIREFOX=pr-13916-firefox-31405661782 \
pnpm test:e2e --headed \
  e2e/tests/desk/defaultPanes.spec.ts \
  e2e/tests/document-actions/delete.spec.ts \
  e2e/tests/document-actions/discardChanges.spec.ts \
  e2e/tests/document-actions/publish.spec.ts \
  e2e/tests/document-actions/restore.spec.ts \
  e2e/tests/document-actions/unpublish.spec.ts \
  e2e/tests/expanded-document/expanded.spec.ts \
  e2e/tests/inputs/array.spec.ts \
  e2e/tests/enhanced-object-dialog/deepLinkPath.spec.ts \
  e2e/tests/inputs/date.spec.ts \
  e2e/tests/pte/referencesInPopover.spec.ts \
  e2e/tests/releases/displayDocument/DisplayedDocument.spec.ts \
  e2e/tests/navbar/createNewDocumentNav.spec.ts \
  e2e/tests/navbar/search.spec.ts \
  e2e/tests/variants/variantTool.spec.ts \
  e2e/tests/vision/vision.spec.ts

Studio: https://e2e-studio-4eado1d17.sanity.dev

[github-actions]

📦 Bundle Stats — sanity

Compared against main (41996fd3) · v6.9.1 (npm)

sanity

Metric	Value	vs main (41996fd)	vs v6.9.1
Internal (raw)	4.18 MB	-	+12.6 KB, +0.3%
Internal (gzip)	1.03 MB	-	+4.1 KB, +0.4%
Bundled (raw)	12.87 MB	-	-33.5 KB, -0.3%
Bundled (gzip)	3.02 MB	-	-38.4 KB, -1.2%
Import time	1.90s	-42ms, -2.2%	+126ms, +7.1%

bin:sanity

Metric	Value	vs main (41996fd)	vs v6.9.1
Internal (raw)	7.1 KB	-	-
Internal (gzip)	2.9 KB	-	-
Bundled (raw)	7.1 KB	-	-
Bundled (gzip)	2.8 KB	-	-
Import time	5ms	+0ms, +0.1%	+0ms, +5.7%

🗺️ View treemap · Artifacts

Details

• Import time regressions over 10% are flagged with ⚠️
• Sizes shown as raw / gzip 🗜️. Internal bytes = own code only. Total bytes = with all dependencies. Import time = Node.js cold-start median.

[github-actions]

⚡️ Editor Performance Report

Updated Mon, 10 Aug 2026 16:03:26 GMT

Benchmark	reference latency of sanity@latest	experiment latency of this branch	Δ (%) latency difference
arrayI18n (simple-en)	33.3 efps (30ms)	33.3 efps (30ms)	+0ms (-/-%)	✅
article (title)	32.3 efps (31ms)	31.3 efps (32ms)	+1ms (+3.2%)	✅
article (body)	27.9 efps (36ms)	67.1 efps (15ms)	-21ms (-58.4%)	✅
article (string inside object)	31.3 efps (32ms)	99.9+ efps (10ms)	-23ms (-70.3%)	✅
article (string inside array)	83.3 efps (12ms)	74.1 efps (14ms)	+2ms (-/-%)	✅
recipe (name)	83.3 efps (12ms)	90.9 efps (11ms)	-1ms (-/-%)	✅
recipe (description)	47.6 efps (21ms)	46.5 efps (22ms)	+1ms (+2.4%)	✅
recipe (instructions)	91.7 efps (11ms)	90.9 efps (11ms)	+0ms (-/-%)	✅
singleString (stringField)	99.9+ efps (9ms)	99.9+ efps (9ms)	+1ms (-/-%)	✅
synthetic (title)	33.3 efps (30ms)	33.3 efps (30ms)	+0ms (-/-%)	✅
synthetic (string inside object)	33.3 efps (30ms)	33.3 efps (30ms)	+0ms (-/-%)	✅

efps — editor "frames per second". The number of updates assumed to be possible within a second.

Derived from input latency. efps = 1000 / input_latency

Detailed information

🏠 Reference result

The performance result of sanity@latest

Benchmark	latency	p75	p90	p99	blocking time	test duration
arrayI18n (simple-en)	30ms	32ms	35ms	45ms	2ms	8.1s
article (title)	31ms	33ms	40ms	53ms	22ms	16.4s
article (body)	36ms	38ms	41ms	82ms	260ms	7.9s
article (string inside object)	32ms	33ms	36ms	46ms	0ms	8.0s
article (string inside array)	12ms	16ms	34ms	68ms	4ms	7.4s
recipe (name)	12ms	15ms	18ms	23ms	55ms	6.2s
recipe (description)	21ms	25ms	29ms	31ms	0ms	4.5s
recipe (instructions)	11ms	13ms	16ms	37ms	0ms	3.5s
singleString (stringField)	9ms	12ms	14ms	22ms	0ms	4.4s
synthetic (title)	30ms	30ms	35ms	61ms	1291ms	12.0s
synthetic (string inside object)	30ms	31ms	34ms	59ms	874ms	9.7s

🧪 Experiment result

The performance result of this branch

Benchmark	latency	p75	p90	p99	blocking time	test duration
arrayI18n (simple-en)	30ms	32ms	33ms	49ms	0ms	9.5s
article (title)	32ms	34ms	41ms	52ms	3ms	15.3s
article (body)	15ms	19ms	32ms	53ms	224ms	6.3s
article (string inside object)	10ms	12ms	17ms	24ms	32ms	6.8s
article (string inside array)	14ms	28ms	39ms	65ms	41ms	7.8s
recipe (name)	11ms	16ms	18ms	21ms	64ms	7.1s
recipe (description)	22ms	25ms	26ms	31ms	0ms	4.4s
recipe (instructions)	11ms	13ms	18ms	40ms	0ms	3.4s
singleString (stringField)	9ms	13ms	17ms	23ms	4ms	4.3s
synthetic (title)	30ms	31ms	32ms	58ms	1244ms	11.4s
synthetic (string inside object)	30ms	31ms	33ms	57ms	860ms	9.7s

📚 Glossary

column definitions

• benchmark — the name of the test, e.g. "article", followed by the label of the field being measured, e.g. "(title)".
• latency — the time between when a key was pressed and when it was rendered. derived from a set of samples. the median (p50) is shown to show the most common latency.
• p75 — the 75th percentile of the input latency in the test run. 75% of the sampled inputs in this benchmark were processed faster than this value. this provides insight into the upper range of typical performance.
• p90 — the 90th percentile of the input latency in the test run. 90% of the sampled inputs were faster than this. this metric helps identify slower interactions that occurred less frequently during the benchmark.
• p99 — the 99th percentile of the input latency in the test run. only 1% of sampled inputs were slower than this. this represents the worst-case scenarios encountered during the benchmark, useful for identifying potential performance outliers.
• blocking time — the total time during which the main thread was blocked, preventing user input and UI updates. this metric helps identify performance bottlenecks that may cause the interface to feel unresponsive.
• test duration — how long the test run took to complete.

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	44.38%	32360 / 72903
🔵	Statements	37.33%	42201 / 113033
🔵	Functions	35.68%	6870 / 19250
🔵	Branches	30.01%	28344 / 94425

File Coverage

No changed files found.

Generated in workflow #64528 for commit 040487c by the Vitest Coverage Report Action