0.5.1

Scarb 0.5.1

Welcome to the release notes for Scarb v0.5.1! This release upgrades Cairo to 2.0.1 and brings some bugfixes.

Compiled contracts and starknet_artifacts files rename

Given the following package manifest:

[package]
name = "PACKAGE"

[[target.starknet-contract]]
name = "TARGET"

Until this version, compiler contracts and the artefacts file followed the following naming scheme:

• TARGET_contract.json
• PACKAGE.starknet_contracts.json

This is incorrect, as when the package defined multiple starknet-contract targets, they will override each other outputs. Since this Scarb version, it will now follow this naming scheme:

• TARGET_contract.json
• TARGET.starknet_contracts.json

Technically, this is a breaking change. But, because of the following reasons, we decided not to cut a major release and treat this as a bugfix:

1. Unless explicitly set TARGET == PACKAGE, so the outcome does not change.
2. It should not be noticeable for humans when they look for files in file managers.
3. While to our knowledge, tools do not rely on these files names anyway and instead look for all *.starknet_contracts.json files in order to look for contract files.

Cairo version

This version of Scarb comes with Cairo v2.0.1.

What's Changed

• Document starknet_artifacts.json file by @cptartur in #454
• Use target_name instead of package_name for starknet_artifacts map file by @maciektr in #459
• Update Cairo to 2.0.1 by @mkaput in #461
• Resolver: add all dependencies to graph by @maciektr in #441

New Contributors

• @cptartur made their first contribution in #454

Full Changelog: v0.5.0...v0.5.1