chore: update @arcadeai/design-system to latest#1042
Merged
Conversation
065ff37 to
fcce5bf
Compare
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
fcce5bf to
d171c81
Compare
d171c81 to
ff11d6f
Compare
ff11d6f to
9751385
Compare
jottakka
approved these changes
Jul 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR updates
@arcadeai/design-systemto the latest published version.It runs a design-system compatibility test gate before opening this PR.
If that gate fails, the workflow stops and no PR is created.
workflow_dispatchNote
Medium Risk
A major design-system version bump can change component APIs, styling, or tokens site-wide even without local code edits; risk is mitigated if the compatibility gate passed but visual/regression checks on docs UI are still worth doing.
Overview
Bumps
@arcadeai/design-systemfrom 3.49.0 to 4.1.0 inpackage.json, with the matching lockfile resolution updates inpnpm-lock.yaml. There are no application source changes in this diff—only the dependency version and lock metadata.This aligns the docs site with the latest published design system (a major minor jump from 3.x to 4.x), after the automated compatibility test gate described in the PR.
Reviewed by Cursor Bugbot for commit 9751385. Bugbot is set up for automated code reviews on this repo. Configure here.