chore: update @cartridge/ui

[tarrencev]

Updates @cartridge/ui dependency to point to commit 1d42129

---

Note

Dependency update

• Points @cartridge/ui to commit 1d42129 in package.json and workspace catalog
• Regenerates pnpm-lock.yaml, updating @cartridge/ui tarball URLs and peer metadata (notably starknet to ^8.5.4) and normalizing eslint resolver entries

^{Written by Cursor Bugbot for commit d415007. This will update automatically on new commits. Configure here.}

[vercel]

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

Project	Deployment	Review	Updated (UTC)
controller-example-next	Ready	Preview	Jan 9, 2026 1:52pm
keychain	Ready	Preview	Jan 9, 2026 1:52pm
keychain-storybook	Ready	Preview	Jan 9, 2026 1:52pm

[claude]

Claude finished @tarrencev's task —— View job

---

Analyzing controller repository changes for documentation updates

Task: Review PR #2309 changes and update documentation in docs-repo if needed.

Todo List:

• Analyze the changed files in PR chore: update @cartridge/ui #2309
• Review the docs-repo directory structure
• Determine if @cartridge/ui dependency update requires documentation changes
• Update documentation if needed or confirm no updates required

Analysis Complete

After reviewing PR #2309 "chore: update @cartridge/ui", I found that this is purely a dependency update that:

1. Updates @cartridge/ui dependency from one commit to another (1d42129) in package.json and pnpm-workspace.yaml
2. Updates lock file - regenerates pnpm-lock.yaml with new tarball URLs and peer metadata
3. No functional changes - no user-facing features, API changes, or breaking changes

Documentation Impact Assessment

No documentation updates are required because:

• This is an internal dependency update with no user-facing changes
• The @cartridge/ui package is an internal design system library used within the keychain interface
• Users don't directly interact with @cartridge/ui components in their applications
• All public APIs and functionality remain unchanged
• The existing documentation in docs-repo accurately reflects the current controller functionality

The documentation structure in docs-repo covers user-facing controller features like authentication, session policies, theming via presets, and integration patterns - none of which are affected by this internal UI library update.

✅ No action required - The documentation is current and accurate.