chore: version packages

[timewave-bot]

Automated PR with updated package versions from changesets

[changeset-bot]

⚠️ No Changeset found

Latest commit: 57cfa50

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

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

Project	Deployment	Preview	Updated (UTC)
valence-ts-example	Ready	Preview	Sep 24, 2025 7:23pm

[gemini-code-assist]

Summary of Changes

Hello @timewave-bot, 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 automates the process of updating package versions based on existing changesets. It primarily focuses on incrementing the patch versions of @valence-protocol/domain-clients-react and @valence-protocol/domain-modal-react to 0.4.1. This update includes a minor bump to the react-dom dependency and ensures that inter-package dependencies are correctly aligned.

Highlights

• Package Version Bumps: The packages @valence-protocol/domain-clients-react and @valence-protocol/domain-modal-react have both been updated to version 0.4.1.
• Dependency Update: The react-dom dependency has been bumped from 18.3.0 to 18.3.1 across the affected packages.
• Inter-package Dependency Alignment: The peerDependencies of @valence-protocol/domain-modal-react have been updated to reflect the new version of @valence-protocol/domain-clients-react.
• Changeset Removal: The temporary changeset file .changeset/bright-times-relate.md has been removed, indicating that its described changes have been applied.

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. ↩

[gemini-code-assist]

Code Review

This pull request contains automated version bumps for the @valence-protocol/domain-clients-react and @valence-protocol/domain-modal-react packages, moving them from version 0.4.0 to 0.4.1. The changes are triggered by a dependency update for react-dom. The package versions, changelogs, and inter-package dependencies have been updated correctly. The changes appear to be consistent with the standard workflow of the changesets tool. I have reviewed the automated changes and found no issues.