Prepare release: 0.12.1

[tarrencev]

Automated changes by create-pull-request GitHub action

---

Note

Publishes version 0.12.1 with a small feature and repo metadata updates.

• Adds configurable errorDisplayMode to @cartridge/controller with modal (default), notification, and silent modes
• Updates CHANGELOG.md with new features, improvements, and development notes
• Bumps versions to 0.12.1 across examples and packages (connector, controller, eslint, keychain, tsconfig)

^{Written by Cursor Bugbot for commit bc9a650. 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 7, 2026 9:00pm
keychain	Ready	Preview	Jan 7, 2026 9:00pm
keychain-storybook	Ready	Preview	Jan 7, 2026 9:00pm

[github-actions]

Claude finished @tarrencev's task —— View job

---

✅ Changelog entry for v0.12.1 completed

I've successfully generated and added a changelog entry for version 0.12.1 of the Cartridge Controller SDK.

Todo List

• Analyze git commit history from v0.12.0 to HEAD
• Read existing CHANGELOG.md format
• Analyze individual commits for changes
• Categorize changes by type and package
• Update CHANGELOG.md with new entry
• Run linting/formatting
• Commit and push changes

Summary of Changes

Found 3 main commits since v0.12.0 and categorized them into the changelog:

✨ New Features:

• @cartridge/controller: Added configurable error display modes with errorDisplayMode option (feat: add configurable error display modes #2312)

🚀 Improvements:

• Enhanced Claude Code integration with structured skill guides (Ignore .worktrees + fix claude settings #2311, docs: enhance CLAUDE.md and add development skills #2310)
• Expanded CLAUDE.md documentation with detailed tech stack info (docs: enhance CLAUDE.md and add development skills #2310)

🔧 Development:

• Added .worktrees to .gitignore for Git worktree support (Ignore .worktrees + fix claude settings #2311)
• Added comprehensive Claude integration permissions and documentation (Ignore .worktrees + fix claude settings #2311, docs: enhance CLAUDE.md and add development skills #2310)

✅ Completed Actions:

• Updated CHANGELOG.md with properly formatted v0.12.1 entry
• All linting and formatting checks passed
• Changes committed and pushed to prepare-release branch

The changelog entry follows the established format and provides clear, user-facing descriptions of the changes included in this release.

---

[claude]

Claude finished @tarrencev's task —— View job

---

✅ Documentation updated for v0.12.1 errorDisplayMode feature

I've successfully analyzed the controller repository changes and updated the documentation to reflect the new errorDisplayMode functionality.

Todo List

• Check if docs-repo directory exists and explore its structure
• Review the controller code changes to understand errorDisplayMode feature
• Analyze existing documentation structure and content
• Determine what documentation updates are needed
• Update configuration.md to include errorDisplayMode option
• Ensure documentation follows existing style and structure

Documentation Updates Made

Updated docs-repo/src/pages/controller/configuration.md:

1. Added to ControllerOptions interface: Added errorDisplayMode?: "modal" | "notification" | "silent" with description

2. Comprehensive Error Display Modes section with:

   • Detailed explanation of all three modes (modal, notification, silent)
   • Behavior descriptions and use case recommendations
   • Special handling for USER_INTERACTION_REQUIRED errors
   • Practical examples for gaming, financial, and custom error handling applications
   • Integration details with the existing toast notification system
   • Best practices and recommended strategies

3. Cross-references: Linked to existing toast notifications documentation

4. Code examples: Multiple TypeScript examples showing different error handling patterns

Analysis Summary

The new errorDisplayMode feature is a significant UX improvement that allows developers to:

• Modal mode: Traditional blocking error dialogs (default)
• Notification mode: Non-blocking toast notifications for better gameplay flow
• Silent mode: Console-only logging for custom error handling

The documentation now comprehensively covers this feature with practical examples, best practices, and integration guidance that follows the existing documentation style and structure.