Skip to content

chore(release): publish v5.24.1#12786

Draft
squiggler-app[bot] wants to merge 1 commit intomainfrom
ci/release-main
Draft

chore(release): publish v5.24.1#12786
squiggler-app[bot] wants to merge 1 commit intomainfrom
ci/release-main

Conversation

@squiggler-app
Copy link
Copy Markdown
Contributor

@squiggler-app squiggler-app Bot commented May 5, 2026

🤖 I have created a release **squib** **squob**

📜 A content release has been created with a changelog document that includes release notes from all PRs included in this release.

Note: Entries in the changelog document can be safely edited and will never be overwritten by automation.

🚀 Steps to release

  1. Mark this PR as ready for review to block open PRs from being merged while release is in progress
  2. Ensure the content release is ready to go and passes validation
  3. Merge this PR

Once this PR is merged, automation will take care of the rest by:

  • Publishing v5.24.1 of all public packages in this repo to the npm registry and tagging as latest
  • Publishing the content release for v5.24.1
  • Tagging, creating, and publishing a GitHub Release for v5.24.1
  • Building and uploading bundles for Auto Updating Studios

Pending changes

Author Message PR Commit Note
squiggler-app[bot] chore(deps): dedupe pnpm-lock.yaml #12764 1880a07 📝 Edit
squiggler-app[bot] fix(deps): Update portabletext #12770 bc47f51 📝 Edit
squiggler-app[bot] chore(deps): update dependency knip to v6 #12782 e5da2ef 📝 Edit
squiggler-app[bot] chore(tests): generate dts tests 🤖 ✨ #12784 2d6b017 📝 Edit

@vercel
Copy link
Copy Markdown

vercel Bot commented May 5, 2026

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

Project Deployment Actions Updated (UTC)
page-building-studio Ready Ready Preview, Comment May 5, 2026 3:24pm
test-studio Ready Ready Preview, Comment May 5, 2026 3:24pm

Request Review

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 5, 2026

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 5, 2026

📦 Bundle Stats — sanity

Compared against main (1880a07c) · v5.24.0 (npm)

sanity

Metric Value vs main (1880a07) vs v5.24.0
Internal (raw) 4.45 MB - -
Internal (gzip) 1.02 MB - -
Import time ❌ node:internal/modules/esm/get_format:185 - -

bin:sanity

Metric Value vs main (1880a07) vs v5.24.0
Internal (raw) 7.1 KB - -
Internal (gzip) 2.9 KB - -
Bundled (raw) 7.1 KB - -
Bundled (gzip) 2.8 KB - -
Import time 6ms +0ms, +0.5% +0ms, +8.2%
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.

@squiggler-app squiggler-app Bot force-pushed the ci/release-main branch from b9d18bf to 1122fd2 Compare May 5, 2026 15:09
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 5, 2026

📚 TypeDoc Generation Result

TypeDoc generated successfully!

  • File size: 8.2M
  • Total exports: 1067
  • Artifact: sanity-typedoc-8bb9e458acffeb7e42a92fde7a06701fd1344b97

The TypeDoc JSON file has been generated and validated. All documentation scripts completed successfully.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 5, 2026

⚡️ Editor Performance Report

Updated Tue, 05 May 2026 15:26:30 GMT

Benchmark reference
latency of sanity@latest
experiment
latency of this branch
Δ (%)
latency difference
arrayI18n (simple-en) 69.0 efps (15ms) 66.7 efps (15ms) +1ms (-/-%)
article (title) 39.2 efps (26ms) 37.0 efps (27ms) +2ms (+5.9%)
article (body) 53.3 efps (19ms) 47.2 efps (21ms) +2ms (+13.1%)
article (string inside object) 50.0 efps (20ms) 45.5 efps (22ms) +2ms (+10.0%)
article (string inside array) 44.4 efps (23ms) 44.4 efps (23ms) +0ms (-/-%)
recipe (name) 99.9+ efps (10ms) 99.9+ efps (10ms) +0ms (-/-%)
recipe (description) 50.0 efps (20ms) 50.0 efps (20ms) +0ms (-/-%)
recipe (instructions) 99.9+ efps (5ms) 99.9+ efps (6ms) +1ms (-/-%)
singleString (stringField) 99.9+ efps (7ms) 99.9+ efps (8ms) +1ms (-/-%)
synthetic (title) 62.5 efps (16ms) 66.7 efps (15ms) -1ms (-6.3%)
synthetic (string inside object) 62.5 efps (16ms) 66.7 efps (15ms) -1ms (-6.3%)

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) 15ms 17ms 21ms 46ms 5ms 5.8s
article (title) 26ms 30ms 33ms 69ms 29ms 7.7s
article (body) 19ms 23ms 29ms 121ms 198ms 5.4s
article (string inside object) 20ms 25ms 30ms 54ms 52ms 6.4s
article (string inside array) 23ms 26ms 33ms 59ms 6ms 6.9s
recipe (name) 10ms 12ms 15ms 30ms 0ms 5.2s
recipe (description) 20ms 23ms 29ms 41ms 0ms 4.5s
recipe (instructions) 5ms 8ms 9ms 10ms 0ms 3.0s
singleString (stringField) 7ms 9ms 12ms 19ms 0ms 4.6s
synthetic (title) 16ms 18ms 20ms 90ms 1255ms 8.9s
synthetic (string inside object) 16ms 18ms 24ms 89ms 1084ms 8.8s

🧪 Experiment result

The performance result of this branch

Benchmark latency p75 p90 p99 blocking time test duration
arrayI18n (simple-en) 15ms 18ms 22ms 40ms 8ms 5.6s
article (title) 27ms 31ms 33ms 68ms 31ms 7.9s
article (body) 21ms 30ms 48ms 96ms 209ms 5.4s
article (string inside object) 22ms 28ms 42ms 70ms 21ms 6.7s
article (string inside array) 23ms 25ms 37ms 58ms 24ms 7.0s
recipe (name) 10ms 12ms 16ms 23ms 0ms 5.3s
recipe (description) 20ms 24ms 32ms 44ms 0ms 4.5s
recipe (instructions) 6ms 10ms 11ms 12ms 0ms 3.0s
singleString (stringField) 8ms 10ms 14ms 25ms 0ms 4.7s
synthetic (title) 15ms 16ms 19ms 97ms 1318ms 9.3s
synthetic (string inside object) 15ms 17ms 28ms 94ms 993ms 8.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
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 5, 2026

Coverage Report

Status Category Percentage Covered / Total
🔵 Lines 41.13% 27699 / 67342
🔵 Statements 33.33% 36268 / 108784
🔵 Functions 29.58% 5475 / 18504
🔵 Branches 24.96% 21850 / 87517
File CoverageNo changed files found.
Generated in workflow #55647 for commit 9051a9c by the Vitest Coverage Report Action

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants