Skip to content

Commit edd2e35

Browse files
RELEASE 0.6.0 (#655)
1 parent fde4822 commit edd2e35

File tree

4 files changed

+7
-6
lines changed

4 files changed

+7
-6
lines changed

CHANGELOG.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,19 +6,19 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
66
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
77

88
# [Unreleased]
9+
# [0.6.0] - 2023-09-13
910

1011
### Forge
1112

1213
#### Added
13-
1414
- `deploy_at` cheatcode
1515
- printing failures summary at the end of an execution
1616
- filtering tests now uses an absolute module tree path — it is possible to filter tests by module names, etc.
17-
- fixed mocking functions even if the contract does not exist
1817

1918
### Fixed
2019

2120
- non-zero exit code is returned when any tests fail
21+
- mock_call works with dispatchers if contract does not exists
2222

2323
### Cast
2424

Cargo.lock

Lines changed: 2 additions & 2 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

Cargo.toml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ members = [
99

1010
[workspace.package]
1111
name = "starknet-foundry"
12-
version = "0.5.0"
12+
version = "0.6.0"
1313
edition = "2021"
1414
repository = "https://github.com/foundry-rs/starknet-foundry"
1515
license = "MIT"

RELEASING.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,8 @@
11
# Instruction For Creating New Starknet Forge Releases
22

33
1. Bump Starknet Foundry version in the top-level `Cargo.toml` file
4-
2. Regenerate locks using `cargo generate-lockfile`
4+
2. Regenerate locks using `cargo update -p forge cast`
5+
3. Update `CHANGELOG.md`
56
3. Merge introduced changes
67
4. Create a new tag in repository with format `vMAJOR.MINOR.PATCH`. This will trigger the release workflow
78
5. Wait for release workflows to pass. A new draft release will be created on GitHub.

0 commit comments

Comments
 (0)