Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

NODE-35, Release bifrost-node v1.2.3 #16

Merged
merged 7 commits into from
Jun 8, 2023
Merged

NODE-35, Release bifrost-node v1.2.3 #16

merged 7 commits into from
Jun 8, 2023

Conversation

dnjscksdn98
Copy link
Member

@dnjscksdn98 dnjscksdn98 commented May 24, 2023 •
edited
Loading

Description

This pull request contains the following changes mentioned below. In addition, this will also resolve some vulnerabilities related to wasmtime.

Native Changes

  • Bump substrate and frontier dependencies to branch bifrost-polkadot-v0.9.39
  • Bump rust toolchain version.
  • Bump dependencies for tests and tools.
  • Move every general workspace dependencies to the root Cargo.toml.
  • Add an independent CLI option that sets the RPC request timeout that's related to EVM transaction logs.
  • Use IdentityAddressMapping for pallet_evm.AddressMapping instead of native IntoAddressMapping.
  • Simplify FindAuthorAccountId's find_author() method.
  • Remove deprecated pallet-random-collective-flip from runtime.

Substrate Changes that impacts runtime codebase

Frontier Changes that impacts runtime codebase

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Something else (simple changes that are not related to existing functionality or others)

Checklist

  • I have selected the correct base branch.
  • I have performed a self-review of my own code.
  • I have made corresponding changes to the documentation.
  • I have made new test codes regarding to my changes.
  • I have no personal secrets or credentials described on my changes.
  • I have run cargo-clippy and linted my code.
  • My changes generate no new warnings.
  • My changes passed the existing test codes.
  • My changes are able to compile.

@dnjscksdn98 dnjscksdn98 added the enhancement New feature or request label May 24, 2023
@dnjscksdn98 dnjscksdn98 self-assigned this May 24, 2023
@dnjscksdn98 dnjscksdn98 changed the base branch from v1.2.3 to main May 24, 2023 07:56
@dnjscksdn98 dnjscksdn98 force-pushed the NODE-35-version-upgrade-to-v-0-9-39 branch from 37b0c23 to b6f50bd Compare May 24, 2023 08:11
@dnjscksdn98 dnjscksdn98 marked this pull request as ready for review May 24, 2023 08:33
@dnjscksdn98 dnjscksdn98 added the do not merge This pull request should not be merged yet label May 30, 2023
@dnjscksdn98 dnjscksdn98 removed the do not merge This pull request should not be merged yet label Jun 8, 2023
@dnjscksdn98 dnjscksdn98 merged commit 0d1811a into main Jun 8, 2023
@dnjscksdn98 dnjscksdn98 deleted the NODE-35-version-upgrade-to-v-0-9-39 branch June 8, 2023 04:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@alstjd0921 alstjd0921 alstjd0921 approved these changes

Assignees

@dnjscksdn98 dnjscksdn98

Labels
enhancement New feature or request
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@dnjscksdn98 @alstjd0921