chore: @mulmoclaude/core の devDependency を 5.5.0 に上げる

[isamu]

Summary

• @mulmoclaude/core devDependency を ^5.4.0 → ^5.5.0（yarn.lock 更新、推移的に google-auth-library の範囲も追従）。
• peerDependencies の範囲は変更なし（core-floor ジョブが下限を引き続き検証）。

Items to Confirm / Review

• マシン高負荷のためローカルの format/lint/typecheck/test は省略し、CI を検証とする。

User Prompt

• git diff を見て問題なければ PR → merge

🤖 Generated with Claude Code

work in sharedapp

Summary by Sourcery

Update the development dependency on @mulmoclaude/core to ^5.5.0.

Enhancements:

• Update the @mulmoclaude/core development dependency to the ^5.5.0 release.

Build:

• Refresh the lockfile to reflect the dependency update and its transitive dependency changes.

Summary by CodeRabbit

• Chores
  • Updated the development tooling package version.

[sourcery-ai]

Sorry @isamu, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 6 hours and 9 minutes by commenting @sourcery-ai review. Upgrade to get a review now.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

@mulmoclaude/core の devDependency を ^5.5.0 に更新し、yarn.lock と関連する推移的依存関係を再解決した変更です。peerDependencies には影響がなく、ローカル検証は未実施のため CI で format/lint/typecheck/test と core-floor ジョブの結果を確認してください。

File-Level Changes

Change	Details	Files
開発用の @mulmoclaude/core を 5.5 系へ更新し、依存ロックを追従させている。	devDependency の要求範囲を ^5.4.0 から ^5.5.0 に変更 yarn.lock の解決結果を更新し、推移的な google-auth-library の範囲も追従 peerDependencies は変更せず、既存の下限互換性検証を維持	package.json yarn.lock

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 0ab4711f-800f-4276-a93c-338caea612d7

📥 Commits

Reviewing files that changed from the base of the PR and between e18c3b2 and 0595f58.

⛔ Files ignored due to path filters (1)

• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (1)

• package.json

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The @mulmoclaude/core devDependency in package.json changed from ^5.4.0 to ^5.5.0. Its peer dependency range remains ^5.4.0.

Changes

Core dependency update

Layer / File(s)	Summary
Update development dependency range package.json	The @mulmoclaude/core devDependency range changed to ^5.5.0. The peer dependency range remains unchanged.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Suggested reviewers: snakajima

Merge Risk: ⚪ Minimal · up to 0595f

この変更では具体的な互換性や動作上の問題は確認できません。ローカル検証は省略されているため、通常のCIチェックが通ることを確認してからマージしてください。

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: updating the @mulmoclaude/core devDependency to version 5.5.0.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

Warning

Some tools did not complete. Review the errors below.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

package.json

Oops! Something went wrong! :(

ESLint: 10.11.0

Error: The 'jiti' library is required for loading TypeScript configuration files. Make sure to install it.
at /.eslint-tmp/node_modules/eslint/lib/config/config-loader.js:145:10
at async loadTypeScriptConfigFileWithJiti (/.eslint-tmp/node_modules/eslint/lib/config/config-loader.js:144:3)
at async loadConfigFile (/.eslint-tmp/node_modules/eslint/lib/config/config-loader.js:265:11)
at async ConfigLoader.calculateConfigArray (/.eslint-tmp/node_modules/eslint/lib/config/config-loader.js:594:23)
at async #calculateConfigArray (/.eslint-tmp/node_modules/eslint/lib/config/config-loader.js:369:19)
at async Promise.all (index 0)
at async findFiles (/.eslint-tmp/node_modules/eslint/lib/eslint/eslint-helpers.js:637:25)
at async ESLint.lintFiles (/.eslint-tmp/node_modules/eslint/lib/eslint/eslint.js:1025:21)
at async Object.execute (/.eslint-tmp/node_modules/eslint/lib/cli.js:386:14)
at async main (/.eslint-tmp/node_modules/eslint/bin/eslint.js:191:19)

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​mulmoclaude/​core@​5.4.0 ⏵ 5.5.0	+1		+1	+1

View full report