feat: V1

CHANGELOG.md

@@ -27,8 +27,9 @@ To use the latest pinned nightly on your CI, modify your Foundry installation st
 
 - [expectEmit](https://github.com/foundry-rs/foundry/pull/4920) will now only work for the next call.
 - expectCall will now only work if the call(s) are made exactly after the cheatcode is invoked.
+- [expectRevert will now work if the next call does revert](https://github.com/foundry-rs/foundry/pull/4945), instead of expecting a revert during the whole test.
+  - This will very likely break your tests. Please make sure that all the calls you expect to revert are external, and if not, abstract them into a separate contract so that they can be called externally and the cheatcode can be used.
 - `-m`, the deprecated alias for `--mt` or `--match-test`, has now been removed.
-- expectRevert will now work if the next call does revert, instead of expecting a revert during the whole test.
 - [startPrank will now override the existing prank instead of erroring](https://github.com/foundry-rs/foundry/pull/4826).
 - [precompiles will not be compatible with all cheatcodes](https://github.com/foundry-rs/foundry/pull/4905).
 - The difficulty and prevrandao cheatcodes now [fail if not used with the correct EVM version](https://github.com/foundry-rs/foundry/pull/4904).

RELEASE_PROCESS.md

@@ -0,0 +1,29 @@
+## Foundry Release Process
+
+## Introduction
+
+From 1.0 onwards, Foundry has a stable release process that is followed for each new version. This document serves as a guide and explanation for the process.
+
+## Step 1 - Testing and benchmarking
+
+Prior to creating a release commit and tagging it for release, we carefully test and benchmark the chosen commit. This is made to ensure that regressions are not made, and measure performance differences across versions.
+
+## Step 2 - Create release commit
+
+Creating a release commit involves the following steps:
+- Crates are version-bumped accordingly.
+- This crate bump gets committed along with the new corresponding tag, e.g `v1.0.0` or `v1.1.3`.
+
+## Step 3 - Create tag and dispatch release workflow
+
+- A tag is created for the new release commit.
+- The tag is then pushed, and the release workflow will be automatically dispatched. The result of the workflow will be a new release with all the relevant files (binary, man pages and changelog).
+
+## Step 4 - Release sanity test
+
+- Once released, the new release is tested to ensure distribution channels (`foundryup`) can download and install the release.
+
+## Miscellaneous
+
+- The working branch is `master`. We do not follow a complicated `staging`/`master` separation, but rather choose to create tags at specific points on the branch history.
+- The release channels are currently simple, and still based on `foundryup`. Different distribution channels might be considered down the line.

abi/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "foundry-abi"
-version = "0.1.0"
+version = "1.0.0"
 edition = "2021"
 license = "MIT OR Apache-2.0"
 readme = "README.md"

anvil/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "anvil"
-version = "0.1.0"
+version = "1.0.0"
 edition = "2021"
 license = "MIT OR Apache-2.0"
 readme = "README.md"

binder/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "foundry-binder"
-version = "0.1.0"
+version = "1.0.0"
 edition = "2021"
 license = "MIT OR Apache-2.0"
 readme = "./README.md"

cast/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "cast"
-version = "0.2.0"
+version = "1.0.0"
 edition = "2021"
 license = "MIT OR Apache-2.0"
 readme = "README.md"

chisel/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "chisel"
-version = "0.1.1"
+version = "1.0.0"
 edition = "2021"
 authors = [
   "clabby <https://github.com/clabby>",

cli/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "foundry-cli"
-version = "0.2.0"
+version = "1.0.0"
 edition = "2021"
 license = "MIT OR Apache-2.0"
 readme = "README.md"

cli/tests/it/integration.rs

@@ -1,9 +1,11 @@
 use foundry_cli_test_utils::{forgetest_external, util::setup_forge_remote};
 
 forgetest_external!(solmate, "transmissions11/solmate");
-forgetest_external!(prb_math, "PaulRBerg/prb-math");
+// Commenting until PRB migration.
+// forgetest_external!(prb_math, "PaulRBerg/prb-math");
 forgetest_external!(prb_proxy, "PaulRBerg/prb-proxy");
-forgetest_external!(solady, "Vectorized/solady");
+// Commenting until solady PR merged
+// forgetest_external!(solady, "Vectorized/solady");
 forgetest_external!(
     geb,
     "reflexer-labs/geb",

common/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "foundry-common"
-version = "0.1.0"
+version = "1.0.0"
 edition = "2021"
 license = "MIT OR Apache-2.0"
 readme = "README.md"

config/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "foundry-config"
-version = "0.2.0"
+version = "1.0.0"
 edition = "2021"
 license = "MIT OR Apache-2.0"
 description = "Foundry configuration"

evm/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "foundry-evm"
-version = "0.2.0"
+version = "1.0.0"
 edition = "2021"
 license = "MIT OR Apache-2.0"
 readme = "../README.md"