Skip to content

Commit

Permalink
RELEASE 0.6.0 (#655)
Browse files Browse the repository at this point in the history
  • Loading branch information
MaksymilianDemitraszek authored Sep 13, 2023
1 parent fde4822 commit edd2e35
Show file tree
Hide file tree
Showing 4 changed files with 7 additions and 6 deletions.
4 changes: 2 additions & 2 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,19 +6,19 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

# [Unreleased]
# [0.6.0] - 2023-09-13

### Forge

#### Added

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

### Fixed

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

### Cast

Expand Down
4 changes: 2 additions & 2 deletions Cargo.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion Cargo.toml
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ members = [

[workspace.package]
name = "starknet-foundry"
version = "0.5.0"
version = "0.6.0"
edition = "2021"
repository = "https://github.com/foundry-rs/starknet-foundry"
license = "MIT"
Expand Down
3 changes: 2 additions & 1 deletion RELEASING.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,8 @@
# Instruction For Creating New Starknet Forge Releases

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

0 comments on commit edd2e35

Please sign in to comment.