Skip to content

Conversation

@tuler
Copy link
Member

@tuler tuler commented Jun 10, 2025

This change makes sure that the cannon package version is the same as the package version.
This is not a big issue in our case because we are not using the publishing of the devnet package. We are saving deployments to the devnet npm package, and using it in the SDK and CLI.

@tuler tuler requested a review from endersonmaia June 10, 2025 18:22
@changeset-bot
Copy link

changeset-bot bot commented Jun 10, 2025

⚠️ No Changeset found

Latest commit: 4ba8fbe

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

@tuler tuler merged commit 117a0c8 into prerelease/v2-alpha Jun 10, 2025
4 checks passed
@tuler tuler deleted the fix/cannonfile branch June 10, 2025 19:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants