chore: release 16.0.0-dev1

[rjan90]

Publish a v16.0.0-dev1 release, so that we can start testing of https://github.com/filecoin-project/FIPs/blob/master/FIPS/fip-0097.md.

[LesnyRumcajs]

@rjan90 This should help with the Cargo Audit in the CI #1597

[rjan90]

This should help with the Cargo Audit in the CI #1597

Oh great, I was a bit confused why that check was not passing.

[rvagg]

rc to dev? confusing, but sure

[github-actions]

Suggested version: 16.0.0-dev1

Comparing to: v16.0.0-dev (diff)

Changes in configuration file(s):

diff --git a/Cargo.toml b/Cargo.toml
index 42739099..91a4f32d 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -10,7 +10,7 @@ members = [
 ]
 
 [workspace.package]
-version = "16.0.0-dev"
+version = "16.0.0-rc1"
 license = "MIT OR Apache-2.0"
 edition = "2021"
 repository = "https://github.com/filecoin-project/builtin-actors"
@@ -137,7 +137,7 @@ fvm_shared = "4.5.1"
 fvm_ipld_encoding = "0.5.0"
 fvm_ipld_blockstore = "0.3.0"
 fvm_ipld_hamt = "0.10.2"
-fvm_ipld_kamt = "0.4.2"
+fvm_ipld_kamt = "0.4.3"
 fvm_ipld_amt = { version = "0.7.3" }
 fvm_ipld_bitfield = "0.7.0"
 

Cutting a Release (and modifying non-markdown files)

This PR is modifying both Cargo.toml and non-markdown files.
The Release Checker is not able to analyse files that are not checked in to master. This might cause the above analysis to be inaccurate.
Please consider performing all the code changes in a separate PR before cutting the release.

Automatically created GitHub Release

A draft GitHub Release has been created.
It is going to be published when this PR is merged.
You can modify its' body to include any release notes you wish to include with the release.

[rjan90]

rc to dev? confusing, but sure

Was a bit unsure what the ideal versioning name here was, since the v16.0.0-rc1 was technically the "F3 led nv25 upgrade", but since we are now adding more scope to the network upgrade, going back to -dev felt like the most correct thing to do.