chore(deps-dev): bump storybook

[Dargon789]

Bumps the npm_and_yarn group with 1 update in the / directory: storybook.

Updates storybook from 8.6.7 to 8.6.15

• Release notes
• Changelog
• Commits

---

updated-dependencies:

• dependency-name: storybook dependency-version: 8.6.15 dependency-type: direct:development dependency-group: npm_and_yarn ...

What changed? Why?

Notes to reviewers

How has it been tested?

Summary by Sourcery

Update frontend tooling dependencies across packages.

Build:

• Bump Storybook dev dependency to version 8.6.15 in onchainkit.
• Upgrade Vite dev dependency to version 6.4.1 in onchainkit and miniapp-manifest-generator, updating the lockfile accordingly.

Chores:

• Refresh pnpm lockfile to reflect updated Storybook and Vite versions.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[gemini-code-assist]

Summary of Changes

Hello @Dargon789, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on routine maintenance by updating key development dependencies. The primary goal is to ensure the project leverages the latest features, bug fixes, and performance enhancements provided by newer versions of Storybook and Vite, thereby improving the development environment and tooling stability.

Highlights

• Dependency Update: Storybook: The storybook development dependency has been updated from version 8.2.9 to 8.6.15 in the packages/onchainkit/package.json file.
• Dependency Update: Vite: The vite development dependency has been updated from version 5.4.21 to 6.4.1 in both packages/miniapp-manifest-generator/package.json and packages/onchainkit/package.json.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[sourcery-ai]

🧙 Sourcery is reviewing your pull request!

---

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.

[github-actions]

Dependency Review

The following issues were found:

• ❌ 2 vulnerable package(s)
• ✅ 0 package(s) with incompatible licenses
• ✅ 0 package(s) with invalid SPDX license definitions
• ✅ 0 package(s) with unknown licenses.
• ⚠️ 5 packages with OpenSSF Scorecard issues.

View full job summary

[gemini-code-assist]

Code Review

This pull request updates dependencies, but the title and description are misleading as they only mention storybook. A significant change is the major version upgrade of vite from v5 to v6 in two different packages, which can introduce breaking changes and should be clearly communicated. Additionally, the storybook update version mentioned in the description is inconsistent with the code changes. To improve clarity and maintainability, the pull request title and description should be updated to accurately reflect all dependency changes.

I am having trouble creating individual review comments. Click here to see my feedback.

packages/miniapp-manifest-generator/package.json (43)

This is a major version upgrade for vite (from v5 to v6). This significant change is not mentioned in the pull request title or description. It's important to accurately document such changes to inform reviewers of potential breaking changes and maintain a clear project history.

packages/onchainkit/package.json (101)

This is a major version upgrade for vite (from v5 to v6). This significant change is not mentioned in the pull request title or description. It's important to accurately document such changes to inform reviewers of potential breaking changes and maintain a clear project history.