chore: update @cartridge/ui

[tarrencev]

Updates @cartridge/ui dependency to point to commit 301966b

[vercel]

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

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

[claude]

Code review

No issues found. Checked for bugs and CLAUDE.md compliance.

[claude]

Claude finished @tarrencev's task —— View job

---

Analyzing Controller Repository Changes

I'll analyze the changes in PR #2346 and determine if any documentation updates are needed in the docs repository.

Task List:

• Review the changed files in the controller repository
• Check what documentation exists in the docs-repo directory
• Determine if @cartridge/ui dependency update requires documentation changes
• Update documentation files if needed, or confirm no updates are required

Analysis of Changes:

The PR updated the @cartridge/ui dependency from one commit to another (commit 301966b) in:

• package.json line 38: "@cartridge/ui": "github:cartridge-gg/ui#301966b"
• pnpm-workspace.yaml line 10: "@cartridge/ui": "github:cartridge-gg/ui#301966b"
• pnpm-lock.yaml: Updated lock file entries to reflect the new commit

This is a pure dependency update without any functional changes to the controller library itself.

Documentation Review:

I found that the @cartridge/ui package is referenced in the documentation at:

• docs-repo/src/pages/controller/examples/react.md:127 - Shows import of Button component from @cartridge/ui

Conclusion:

No documentation updates are required.

The PR is a pure dependency update that points to a newer commit of the @cartridge/ui library. Since:

1. The documentation doesn't reference specific version numbers or commit hashes of @cartridge/ui
2. The API usage shown in the documentation (importing Button component) remains the same
3. This is an internal dependency update that doesn't affect the public API of the controller
4. No breaking changes or new features are introduced that would require documentation updates

The existing documentation remains accurate and up-to-date with this dependency change.

---