v1.0.3

1.0.3 (2022-12-10)

✨ Features

• Introducing our brand new re-architected VSCode extension (README)
• All of our tools (REPL, LSP, Clarinet) are now directly derived from the canonical Clarity VM (#512, #535, #544)
• Ability to trigger chainhooks from unit tests (#564)
• Deno integration upgraded and revisited (#511)
• Ability to specify Deno import maps (#511)
• Ability to specify TS config files (#555)
• Ability to cache Deno libraries locally (a2c2ded3)
• Bitcoin deployment plans now supports transfers to P2WPKH addresses (c50a4c27)
• Ability to detect outdated deployment plans and display diffs (#365)

🐞 Bug fixes

A myriad of issues were addressed in this new version, the most notable being:

• Cannot make http request from within clarinet test (#566)
• Clarinet CPU usage spiking to 100% when using clarinet integrate (#545)
• Clarinet console crashes when it errors (#541)
• Unhandled Division By Zero exception (#525)
• Handle errors from callReadOnlyFn in tests (#407)
• Arithmetic underflow crashes clarity-repl instead of displaying error (#471)
• Improve debugability of chain.mine_block() (#91)

📚 Documentation

• Added new example - How to use Chainhooks for indexing data (cdeca648)
• Added OpenAPI spec for Chainhooks (01e8979c)

🚨 Backward compatibility

Clarinet v1.0.0 is not backwards-compatible with older versions of the Clarinet deno library. If you are upgrading Clarinet to Clarinet v1.0.2, you will need to enter the following import command in your test files to perform this update.

import { … } from 'https://deno.land/x/[email protected]/index.ts';

Note The v1.0.0 library is not compatible with Clarinet versions <= 0.33.0. Prior versions of the library also will not be compatible with versions >= 1.0.0 of Clarinet because the layer in charge of the communication between Typescript and Rust was upgraded.
If you are using Clarinet in a Github Action, and using the tag latest (now pointing to v1.0.0), the tests will fail if the import upgrade task is not performed. If you do not want to upgrade, this is possible; however, you will need to specify the docker tag v0.33.0, instead of latest.

v1.0.2

1.0.2 (2022-10-10)

✨ Features

• Introducing our brand new re-architected VSCode extension (README)
• All of our tools (REPL, LSP, Clarinet) are now directly derived from the canonical Clarity VM (#512, #535, #544)
• Ability to trigger chainhooks from unit tests (#564)
• Deno integration upgraded and revisited (#511)
• Ability to specify Deno import maps (#511)
• Ability to specify TS config files (#555)
• Ability to cache Deno libraries locally (a2c2ded3)
• Bitcoin deployment plans now supports transfers to P2WPKH addresses (c50a4c27)
• Ability to detect outdated deployment plans and display diffs (#365)

🐞 Bug fixes

A myriad of issues were addressed in this new version, the most notable being:

• Cannot make http request from within clarinet test (#566)
• Clarinet CPU usage spiking to 100% when using clarinet integrate (#545)
• Clarinet console crashes when it errors (#541)
• Unhandled Division By Zero exception (#525)
• Handle errors from callReadOnlyFn in tests (#407)
• Arithmetic underflow crashes clarity-repl instead of displaying error (#471)
• Improve debugability of chain.mine_block() (#91)

📚 Documentation

• Added new example - How to use Chainhooks for indexing data (cdeca648)
• Added OpenAPI spec for Chainhooks (01e8979c)

🚨 Backward compatibility

Clarinet v1.0.0 is not backwards-compatible with older versions of the Clarinet deno library. If you are upgrading Clarinet to Clarinet v1.0.2, you will need to enter the following import command in your test files to perform this update.

import { … } from 'https://deno.land/x/[email protected]/index.ts';

Note The v1.0.0 library is not compatible with Clarinet versions <= 0.33.0. Prior versions of the library also will not be compatible with versions >= 1.0.0 of Clarinet because the layer in charge of the communication between Typescript and Rust was upgraded.
If you are using Clarinet in a Github Action, and using the tag latest (now pointing to v1.0.0), the tests will fail if the import upgrade task is not performed. If you do not want to upgrade, this is possible; however, you will need to specify the docker tag v0.33.0, instead of latest.

v1.0.0

1.0.0 (2022-10-06)

✨ Features

• Introducing our brand new re-architected VSCode extension (README)
• All of our tools (REPL, LSP, Clarinet) are now directly derived from the canonical Clarity VM (#512, #535, #544)
• Ability to trigger chainhooks from unit tests (#564)
• Deno integration upgraded and revisited (#511)
• Ability to specify Deno import maps (#511)
• Ability to specify TS config files (#555)
• Ability to cache Deno libraries locally (a2c2ded3)
• Bitcoin deployment plans now supports transfers to P2WPKH addresses (c50a4c27)
• Ability to detect outdated deployment plans and display diffs (#365)

🐞 Bug fixes

A myriad of issues were addressed in this new version, the most notable being:

• Cannot make http request from within clarinet test (#566)
• Clarinet CPU usage spiking to 100% when using clarinet integrate (#545)
• Clarinet console crashes when it errors (#541)
• Unhandled Division By Zero exception (#525)
• Handle errors from callReadOnlyFn in tests (#407)
• Arithmetic underflow crashes clarity-repl instead of displaying error (#471)
• Improve debugability of chain.mine_block() (#91)

📚 Documentation

• Added new example - How to use Chainhooks for indexing data (cdeca648)
• Added OpenAPI spec for Chainhooks (01e8979c)

🚨 Backward compatibility

Clarinet v1.0.0 is not backwards-compatible with older versions of the Clarinet deno library. If you are upgrading Clarinet to Clarinet v1.0.2, you will need to enter the following import command in your test files to perform this update.

import { … } from 'https://deno.land/x/[email protected]/index.ts';

Note The v1.0.0 library is not compatible with Clarinet versions <= 0.33.0. Prior versions of the library also will not be compatible with versions >= 1.0.0 of Clarinet because the layer in charge of the communication between Typescript and Rust was upgraded.
If you are using Clarinet in a Github Action, and using the tag latest (now pointing to v1.0.0), the tests will fail if the import upgrade task is not performed. If you do not want to upgrade, this is possible; however, you will need to specify the docker tag v0.33.0, instead of latest.

Contributors

@aviculturist
@criadoperez
@CharlieC3
@csgui
@dabuchera
@dtrodrigues
@empeje
@friedger
@hstove
@hugocaillard
@jdbender66
@jhammond2012
@josecanhelp
@LakshmiLavanyaKasturi
@lgalabru
@LNow
@mcintyre94
@michaelgold
@moodmosaic
@obycode
@rafaelcr
@reedrosenbluth
@whoabuddy
@zone117x

v0.33.0

0.33.0 (2022-07-22)

✨ Features

• Enhance hyperchain integration (#432, #480, #494 )
• Display microblocks in clarinet terminal UI (77535aa6)
• Improve block / microblock fork handling (#480)
• Various chainhooks improvements (#429)
• Suggest changes to default deployment plans when updates available (#488, #489)

🧹 Chores

• Migrate to mono-repo layout (#481)
• Revisit CI and release process (423c3d36)
• deps:
  • bump crossbeam-utils in /components/stacks-devnet-js (9a0dedfd)
  • bump thread_local in /components/stacks-devnet-js (a6b5065f)
  • bump nix in /components/stacks-devnet-js (f453b4aa)
• docs:
  • README.md. Removed depends_on() field in the clarinet.toml file and added success message for clarinet check command. (84d0a327)

Credits

@CharlieC3
@LakshmiLavanyaKasturi
@lgalabru
@moodmosaic

v0.32.0

0.32.0 (2022-06-23)

✨ Features

• Experimental: run a Hyperchain node in your local Devnet
• Experimental: observe stacks transactions and bitcoin transactions, using chainhooks (see examples/cbtc)
• Experimental: support for Bitcoin transactions in deployment plans (see examples/cbtc)
• Ability to deploy requirements on Devnet / Testnet
• Support for custom contract-call in deployment plans (see examples/cbtc)
• Launch an empty clarinet console when no manifest can be found
• Add ::read command to clarinet console

🐞 Bug fixes

• Various adjustments stabilizing the automatic dependency graph inference
• Display eventual contracts errors when clarinet test fails
• Polish Stacks + Bitcoin faucets configurability on Devnet
• Fix alias for clarinet deployment

🚨 Backward compatibility issues

• The deployment plans files format changed, a backward compatibility patch is in place, but re-generating existing plans would be preferable.

Credits

@fariedt
@lgalabru
@mcintyre94
@moodmosaic
@obycode

v0.31.1

0.31.1 (2022-05-27)

Bug Fixes

• code coverage not including initial executions (6089e86)
• display errors from parsing (517a3fa)
• explorer, noneCV (3dd1142)
• usage of default deployment files (c6b1f8c)
• use [email protected] lib in generated tests (74b1b99), closes #381
• wrong network (a631268)

v0.31.0

0.31.0 (2022-05-24)

Bug Fixes

• The vs-code extension issues use of unresolved contract *** should now be a thing from the past, and you should get your errors in line, whatever the directory layout of your project in vscode is https://github.com/hirosystems/clarity-lsp/issues/76
• Memory leak that would crash a CI runner on extensive test suites #324
• Various bugs related to usage of requirements, which should now be stable

Features

• Introducing deployment plans: this is opening a lot of neat possibilities for the clarinet hard core hackers out there, while being invisible for others #312
• Sunsetting “depends_on”: this attribute is no longer needed in your Clarinet manifests
• 2x to 3x speed improvement when executing test suites
• Costs reports and ETA when deploying contracts
• Upgrade to clarity-repl v0.28 with all of its new features and fixes

🚨 Compatibility Issue

clarinet v0.31 is not backwards compatible with older versions of the clarinet deno library. If you’re using clarinet v0.31.0, you need to import

import { … } from 'https://deno.land/x/[email protected]/index.ts';

in your test files.
This v0.31.0 library is not compatible with clarinet’s versions <= 0.30.0, and the prior versions of the library won’t be compatible with versions >= 0.31.0 of Clarinet - the layer in charge of the communication between typescript and rust was upgraded.
If you’re using clarinet as a CI and using the latest tag (now pointing to v0.31.0) , then your tests will end up failing if the import upgrade is not done. If you don’t want to upgrade, this is possible, you just need to specify the docker tag v0.30.0, instead of latest.

v0.30.0

0.30.0 (2022-05-13)

Bug Fixes

• Resolve issue with unordered contracts causing errors in console

Features

• Add support for debugging in VS Code (and other IDEs that support the DAP)

Credits

• @jhammond2012
• @lgalabru
• @moodmosaic (clarity-repl)
• @obycode

v0.29.1

0.29.1 (2022-05-03)

Bug Fixes

• fixed problem with contract ordering in lsp (12bccc5)

v0.29.0

0.29.0 (2022-04-21)

Bug Fixes

• Fix issue with telemetry prompt on windows (0af8fe9), closes #317
• remove caveman dbg statement (bd830f9)
• remove warnings about manifest file (49edfd4)

Features

• add new costs synthesis table (d8f5f29)
• add boot_contracts config (c1cab93)
• add tx_per_block and improve formatting (1fc6d4f)

Credits

• @friedger
• @lgalabru
• @LNow
• @mcintyre94
• @obycode