chore: update clarinet sdk to v2

[hugoclrd]

Description

• Update @hirosystems/clarinet-sdk and vitest-environment-clarinet to v2
  • The clarinet-sdk now relies on the deployment plan (default.simnet-plan.yaml) hence why there's this new file
• Also updated vite and vitest as part of this PR
  • Adapt the vitest config

[CLAassistant]

All committers have signed the CLA.

[moodmosaic]

LGTM 👍

We're currently using those also in stacks-network/stacks-core#4550.

[MarvinJanssen]

Thanks @hugocaillard!

[MarvinJanssen]

Apologies @hugocaillard could you update packages/clarunit/CHANGELOG.md as well?

[hugoclrd]

Hey @MarvinJanssen
Happy to, but I'm used to updating changelog on release, and this PR didn't update the version.
Do you want this PR to also bump the version?
Since you're recommending conventional commit, would you consider using something like

• generate-changelog
• conventional-changelog-cli

Definitely don't want to overkill of course, let's take the simplest solution

[MarvinJanssen]

I think it is necessary to publish the changes to npm. Perhaps @wileyj can chime in since he set it up.

[hugoclrd]

Ok indeed it looks like neither of us can publish. Could be nice to have it in the CI

[wileyj]

@hugocaillard @MarvinJanssen published (we have an issue to autopublish, low priority recently): https://www.npmjs.com/package/@stacks/clarunit

[hugoclrd]

Thanks @wileyj
Can you push the version bump on github as well? thx

[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: ***@***.***>

[MarvinJanssen]

Thanks @wileyj!