Integrate changesets into the repository#1364
Merged
Merged
Conversation
ahnafalfariza
approved these changes
Jul 15, 2025
roman009
approved these changes
Jul 16, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR introduces changesets to the repository, enabling automated and versioned releases across packages. With this setup, each meaningful change can be documented with a changeset file, which is then used to determine version bumps and generate changelogs. Once changes are merged into the main branch, changesets will handle publishing the updated packages to npm, ensuring a consistent and transparent release process. This also improves collaboration by making it clear what changes are included in each release and simplifies maintenance in a monorepo environment like
wallet-selector.