New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: update clarinet sdk to v2 #4
chore: update clarinet sdk to v2 #4
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
We're currently using those also in stacks-network/stacks-core#4550.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @hugocaillard!
Apologies @hugocaillard could you update |
Hey @MarvinJanssen Definitely don't want to overkill of course, let's take the simplest solution |
I think it is necessary to publish the changes to npm. Perhaps @wileyj can chime in since he set it up. |
Ok indeed it looks like neither of us can publish. Could be nice to have it in the CI |
@hugocaillard @MarvinJanssen published (we have an issue to autopublish, low priority recently): https://www.npmjs.com/package/@stacks/clarunit |
Thanks @wileyj |
meant to do that, thanks for reminder
…On Wed, Apr 3, 2024 at 11:20 AM Hugo C ***@***.***> wrote:
Thanks @wileyj <https://github.com/wileyj>
Can you push the version bump on github as well? thx
—
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAVXIHCU2HJ7V4X3KS34ELTY3RB7JAVCNFSM6AAAAABFK4H4BGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZVGI4TIMZUHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Thanks @wileyj! |
Description