search

ava-labs / icm-services

Services for relaying Avalanche ICM messages between L1s
Other
24 stars 19 forks source link

Bump github.com/ava-labs/subnet-evm from 0.6.10 to 0.6.11 #528

Closed dependabot[bot] closed 1 month ago

dependabot[bot] commented 1 month ago

Bumps github.com/ava-labs/subnet-evm from 0.6.10 to 0.6.11.

Release notes

Sourced from github.com/ava-labs/subnet-evm's releases.

v0.6.11

This release focuses on Standalone DB and database configs.

This version is backwards compatible to v0.6.0. It is optional, but encouraged.

The plugin version is unchanged at 37 and is compatible with AvalancheGo versions v1.11.12.

Updates

  • Added Standalone DB creation in chain data directory (~/.avalanchego/chainData/{chain-ID}/db/). Subnet-EVM will create seperate databases for chains by default if there is no accepted blocks previously (ava-labs/subnet-evm#1354)
  • Refactored Warp Backend to support new payload types (ava-labs/subnet-evm#1292)
  • Refactored TrieDB reference root configuration (ava-labs/subnet-evm#1366)
  • Bumped AvalancheGo dependency to v1.11.12
  • Bumped minimum Golang version to v1.22.8

Configs

  • Added following new database options:
    • "use-standalone-database" (bool): If true it enables creation of standalone database. If false it uses the GRPC Database provided by AvalancheGo. Default is nil and creates the standalone database only if there is no accepted block in the AvalancheGo database (node has not accepted any blocks for this chain)
    • "database-type" (string): Specifies the type of database to use. Must be one of pebbledb, leveldb or memdb. memdb is an in-memory, non-persisted database. Default is pebbledb
    • "database-config-file" (string): Path to the database config file. Config file is changed for every database type. See docs for available configs per database type. Ignored if --config-file-content is specified
    • "database-config-file-content" (string): As an alternative to database-config-file, it allows specifying base64 encoded database config content
    • "database-path" (string): Specifies the directory to which the standalone database is persisted. Defaults to "$HOME/.avalanchego/chainData/{chainID}"
    • "database-read-only" (bool) : Specifies if the standalone database should be a read-only type. Defaults to false

Fixes

What's Changed

New Contributors

... (truncated)

Commits


Dependabot compatibility score

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)
dependabot[bot] commented 1 month ago

Looks like github.com/ava-labs/subnet-evm is up-to-date now, so this is no longer needed.