Bump ink_primitives from 3.0.0-rc8 to 3.0.0-rc9

Created by: dependabot[bot]

Bumps ink_primitives from 3.0.0-rc8 to 3.0.0-rc9.

Release notes

Sourced from ink_primitives's releases.

ink! 3.0.0 RC 9

Version 3.0-rc9

This is the 9th release candidate for ink! 3.0.

Breaking Changes

We removed all data structures other than Mapping from the public ink! API

This is a drastic breaking change; it was no easy decision for us. It affects Lazy and Memory as well. The rationale behind this change, as well as some notes on migrating existing contracts, are explained in #1111 and #1137.

If you used Memory in your contract, you can achieve the same functionality by passing this data via arguments. If you think there's a case to be made for bringing it back, please get in contact with us.

If you use ink_storage::Mapping in your contract, you need to initialize the data structure using the helper function ink_lang::utils::initialize_contract(…). For more code examples you can take a look at our examples, e.g. erc20.

Please upgrade scale-info and parity-scale-codec in your contract's dependencies

In this release candidate we upgraded scale-info and parity-scale-codec. You have to use a compatible version in your contract's Cargo.toml as well; cargo-contract will throw an error otherwise.

The Cargo.toml should contain

scale-info = { version = "2", default-features = false, features = ["derive"], optional = true }
scale = { package = "parity-scale-codec", version = "3", default-features = false, features = ["derive", "full"] }

Added

  • Export ink_lang::utils::initialize_contract(…) - #1077.
  • Add get_owner() function to dns example contract - #1118 (thanks @​agryaznov).
  • Improved usage documentation of ink_storage::Mapping - #1138.

Changed

  • Updated to parity-scale-codec = "3" and scale-info = "2" - #1132.

Removed

  • Remove collection and lazy modules from public ink! API - #1111.
  • Remove Memory from public ink! API - #1137.

Fixed

  • Fix bug with referencing two external trait definitions - #1141.
  • Explicitly specify trait in dispatching - #1131 (thanks @​xgreenx).

... (truncated)

Changelog

Sourced from ink_primitives's changelog.

Version 3.0-rc9

This is the 9th release candidate for ink! 3.0.

Breaking Changes

We removed all data structures other than Mapping from the public ink! API

This is a drastic breaking change; it was no easy decision for us. It affects Lazy and Memory as well. The rationale behind this change, as well as some notes on migrating existing contracts, are explained in #1111 and #1137.

If you used Memory in your contract, you can achieve the same functionality by passing this data via arguments. If you think there's a case to be made for bringing it back, please get in contact with us.

If you use ink_storage::Mapping in your contract, you need to initialize the data structure using the helper function ink_lang::utils::initialize_contract(…). For more code examples you can take a look at our examples, e.g. erc20.

Please upgrade scale-info and parity-scale-codec in your contract's dependencies

In this release candidate we upgraded scale-info and parity-scale-codec. You have to use a compatible version in your contract's Cargo.toml as well; cargo-contract will throw an error otherwise.

The Cargo.toml should contain

scale-info = { version = "2", default-features = false, features = ["derive"], optional = true }
scale = { package = "parity-scale-codec", version = "3", default-features = false, features = ["derive", "full"] }

Added

  • Export ink_lang::utils::initialize_contract(…) - #1077.
  • Add get_owner() function to dns example contract - #1118 (thanks @​agryaznov).
  • Improved usage documentation of ink_storage::Mapping - #1138.

Changed

  • Updated to parity-scale-codec = "3" and scale-info = "2" - #1132.

Removed

  • Remove collection and lazy modules from public ink! API - #1111.
  • Remove Memory from public ink! API - #1137.

Fixed

  • Fix bug with referencing two external trait definitions - #1141.
  • Explicitly specify trait in dispatching - #1131 (thanks @​xgreenx).
  • Make rust-analyzer expand ink! macros without warning - #1107.

... (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 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)

Merge request reports