ChainSafe / fil-actor-states

State handling crates for the Filecoin Actors
Apache License 2.0
3 stars 2 forks source link

chore(deps): update fvm_shared requirement from ~2.6 to ~4.1 #288

Closed dependabot[bot] closed 4 months ago

dependabot[bot] commented 4 months ago

Updates the requirements on fvm_shared to permit the latest version.

Changelog

Sourced from fvm_shared's changelog.

FVM M2 Test Network Release Process

Deploy a test network, you'll need to:

  1. Release the FVM.
  2. Release the actors (updating the FVM if necessary).
  3. Update the FVM in the FFI.
  4. Update the FFI & actors in lotus.

Release the FVM

Cut an alpha release of the FVM (filecoin-project/ref-fvm) per the release process.

If the builtin-actors isn't using the latest version of version of fvm_shared, fvm_sdk, or any of the ipld/ crates:

  1. Clone the filecoin-project/builtin-actors repo.
  2. Checkout the next branch.
  3. Update the fvm* crates (cargo upgrade --workspace fvm fvm_sdk ...).
  4. Make a PR, wait for CI, merge, etc.

Release the Actors

Create a dev/$date-m2 [pre-release][releases] of the next branch. This will run the [release workflow][release-workflow] and will build a new bundle.

  • There's no need to bump the actor crate versions, just cut a release "tag" on github.
  • Creating a git tag isn't sufficient, you'll need to create the release on github to actually trigger the build.

Update the FFI

  1. Clone filecoin-project/filecoin-ffi, checkout the feat/m2 branch.
  2. Change to the rust/ directory, and update all FVM crates: cargo upgrade fvm fvm_shared fvm_ipld_blockstore fvm_ipld_encoding.
  3. Make a PR to feat/m2, etc.

Update Lotus

First, update and rebuild the FFI:

  1. Clone filecoin-project/lotus, checkout the experimental/fvm-m2branch.
  2. Change to the extern/filecoin-ffi submodule, git fetch, then checkout the experimental/fvm-m2 branch.
  3. Run make FFI_BUILD_FROM_SOURCE=1 inside extern/filecoin-ffi to build it. You may need to install some build dependencies, take a look at the FFI README.

Then, update the actors:

  1. Change directory to build/actors in lotus.
  2. Run ./pack.sh v8 dev/$date-m2 (where dev/$date-m2 is the actor's release tag you just created).

Build and test lotus:

  1. Build lotus (run make in the repo root).
  2. Try to start a devnet.

... (truncated)

Commits


Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
hanabi1224 commented 4 months ago

@dependabot ignore this dependency

dependabot[bot] commented 4 months ago

OK, I won't notify you about fvm_shared again, unless you re-open this PR.