v1.7.0

1.7.0 (2023-06-14)

✨ New features

• Upgrade clarity-vm and handle epoch 2.4 (0c8de5b)
• Improve clarity test code coverage and handle code branches (#1030) (13d4502)

v1.6.2

chore: bump version to 1.6.2 (#1019)

v1.6.1

Merge pull request #1013 from hirosystems/release/next

chore: bump version to 1.6.1

v1.6.0

1.6.0 (2023-05-09)

✨ New Features

• Allow specifying filename with test coverage (5977ec1)

🚨 Breaking change

• Set genesis block time to current system time (6d89401)

Previously whenever a simnet was started, the genesis block’s time (the burn_block_time field) was set to 0. Subsequent blocks were assigned a time of 1800 * block_height, because they were based off of a genesis block with a time of 0.

Because this isn’t a very realistic genesis block time, we’ve updated the genesis block to use the current system time. Subsequent blocks are still given times at an interval of 1800ms, but they are based off of the genesis block’s time, so they are calculated as genesis.burn_block_time + (1800 * block_height).

While this is unlikely to be a breaking change in most places, any code that relies on a specific block time could be impacted by this change.

🐞 Bug Fixes

• Handle clarity-version in the dependency detector (f91f8f8)
• Handle LSP default configuration (61792b6)
• Use chrono to get genesis time (504b4fd)
• Don't prompt to write files to project dir when using --allow-write flag (#981) (d5c654e)
• Remove [[ustx_balance]] from subnet config to work with subnets v0.5.0 (7f0e235)

Credits

• @davidmurdoch
• @hugocaillard
• @jbencin
• @lgalabru
• @MicaiahReid
• @obycode

v1.5.4

Merge pull request #954 from davidmurdoch/patch-1

docs: format vscode's `launch.json` as JSON5

v1.5.3

Merge pull request #942 from hirosystems/release/next

chore: bump version

v1.5.2

Merge branch 'main' into develop

v1.5.1

1.5.0 (2023-03-14)

✨ Features

• Improved support for launching a subnet in clarinet integrate (6fc2c540)
• clarinet integrate is now relying on the latest stacks-node 2.1 and on bitcoind v24 - ideal if you are exploring ordinals and working with ord (b1264e61)
• Update chainhooks predicate schemas (038ff1f)
• Handle Clarity version and epoch for requirements (b667a1c1)

🐞 Bug fixes

• Various improvements in auto-completion (2e90ace, 17752be, 8e9bcc9)
• Fixes on the cBTC example.

📚 Documentation

• Added deployment plans documentation (dabf1fd)
• Added links to documentation and issues (10a597b)
• Fixed various other minor documentation issues (2b6d301, d0f5c47)

🚨 Breaking change

• The enable_next_features setting for enabling Stacks 2.1 is no longer required, as the code for Stacks 2.1 was recently merged.
• The epoch 2.1 management could be breaking some unit tests if they were hard coding block heights in your unit tests.
• Chainhook files should now be specified with JSON (instead of YAML) and these same JSON specifications can be used for API registration (POST /v1/chainhooks endpoint). We're starting adding documentation on this repository.

Credits

• @DieracDelta
• @hugocaillard
• @LakshmiLavanyaKasturi
• @lgalabru
• @max-crawford
• @mefrem
• @obycode
• @sabbyanandan
• @wileyj
• @whoabuddy

v1.5.0

1.5.0 (2023-03-14)

✨ Features

• Improved support for launching a subnet in clarinet integrate (6fc2c540)
• clarinet integrate is now relying on the latest stacks-node 2.1 and on bitcoind v24 - ideal if you are exploring ordinals and working with ord (b1264e61)
• Update chainhooks predicate schemas (038ff1f)
• Handle Clarity version and epoch for requirements (b667a1c1)

🐞 Bug fixes

• Various improvements in auto-completion (2e90ace, 17752be, 8e9bcc9)
• Fixes on the cBTC example.

📚 Documentation

• Added deployment plans documentation (dabf1fd)
• Added links to documentation and issues (10a597b)
• Fixed various other minor documentation issues (2b6d301, d0f5c47)

🚨 Breaking change

• The enable_next_features setting for enabling Stacks 2.1 is no longer required, as the code for Stacks 2.1 was recently merged.
• The epoch 2.1 management could be breaking some unit tests if they were hard coding block heights in your unit tests.
• Chainhook files should now be specified with JSON (instead of YAML) and these same JSON specifications can be used for API registration (POST /v1/chainhooks endpoint). We're starting adding documentation on this repository.

Credits

• @DieracDelta
• @hugocaillard
• @LakshmiLavanyaKasturi
• @lgalabru
• @max-crawford
• @mefrem
• @obycode
• @sabbyanandan
• @wileyj
• @whoabuddy

v1.4.2

Merge pull request #868 from hirosystems/rc/next

Release next