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.

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

Bump frame-system from polkadot-v1.6.0 to polkadot-v1.7.1 #534

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 20, 2024

Bumps frame-system from polkadot-v1.6.0 to polkadot-v1.7.1.

Release notes

Sourced from frame-system's releases.

Polkadot v1.7.1

This release contains the changes from polkadot-v1.7.0 to polkadot-v1.7.1.

Rust compiler versions

This release was built and tested against the following versions of rustc. Other versions may work.

Rust Stable: rustc 1.75.0 (82e1608df 2023-12-21) Rust Nightly: rustc 1.77.0-nightly (ef71f1047 2024-01-21)

Changes

Changelog for Node Operator.

#3385: Do not stall finality on spam disputes

This PR fixes the issue that periodically caused finality stalls on Kusama due to disputes happening there in combination with disputes spam protection mechanism.

See: paritytech/polkadot-sdk#3345

Polkadot v1.7.0

This release contains the changes from polkadot-v1.6.0 to polkadot-v1.7.0.

Rust compiler versions

This release was built and tested against the following versions of rustc. Other versions may work.

Rust Stable:  rustc 1.74.0 (79e9716c9 2023-11-13)
Rust Nightly: rustc 1.75.0-nightly (9d83ac217 2023-10-31)

Runtimes

Westend

🏋️ Runtime size:             1.650 MB (1,730,647 bytes)
🗜 Compressed:               Yes, 79.22%
✨ Reserved meta:            OK - [6D, 65, 74, 61]
🎁 Metadata version:         V14
🔥 Core version:             westend-1007000 (parity-westend-0.tx24.au2)
🗳️ system.setCode hash:      0xe8db5e7b5b9edcc68c2275a2e64b2092b36f19159dbb55d4c7574198f325383e
🗳️ authorizeUpgrade hash:    0x30422f3a96a9a2a81e88c0ba936ba859fa4e9bcb9d06b4febe4a21bd76d2f46f
🗳️ Blake2-256 hash:          0x085f68ab9991262334e944c078caeb8b20fede674dc1fca5fdc5fd7d4dd35e3a
📦 IPFS:                     https://www.ipfs.io/ipfs/QmSmmQXCkADd8f5JVese9Cp8xnuo8F3UdLzURQnD7QVUDU

... (truncated)

Changelog

Sourced from frame-system's changelog.

Release

The outputs of a release are the polkadot and polkadot-parachain node binaries, the runtimes for Westend & Rococo and their system parachains, and new crate versions published to crates.io.

Setup

We have two branches: master and stable. master is the main development branch where normal Pull Requests are opened. Developers need to mostly only care about this branch.
The stable branch contains a version of the code that is ready to be released. Its contents are always audited. Merging to it is restricted to Backports.

Versioning

We are releasing multiple different things from this repository in one release, but we don't want to use the same version for everything. Thus, in the following we explain the versioning story for the crates, node and Westend & Rococo. To easily refer to a release, it shall be named by its date in the form stableYYMMDD.

Crate

We try to follow SemVer 2.0.0 as best as possible for versioning our crates. SemVer requires a piece of software to first declare a public API. The public API of the Polkadot SDK is hereby declared as the sum of all crates' public APIs.

Inductively, the public API of our library crates is declared as all public items that are neither:

  • Inside a __private module
  • Documented as "unstable" or "experimental" in the first line of docs
  • Bear unstable or experimental in their absolute path

Node

The versioning of the Polkadot node is done most of the time by only incrementing the minor version. The major version is only bumped for special releases and the patch can be used for an out of band release that fixes some critical bug. The node version is not following SemVer. This means that the version doesn't express if there are any breaking changes in the CLI interface or similar. The node version is declared in the NODE_VERSION variable.

Westend & Rococo

For the these networks, in addition to incrementing the Cargo.toml version we also increment the spec_version and sometimes the transaction_version. The spec version is also following the node version. Its schema is: M_mmm_ppp and for example 1_002_000 is the node release 1.2.0. This versioning has no further meaning, and is only done to map from an on chain spec_version easily to the release in this repository.
The Westend testnet will be updated to a new runtime every two weeks with the latest nightly release.

Backports

From master to stable

... (truncated)

Commits
  • 70e569d move prdoc file to the release folder
  • 5fcebde Bump node version to 1.7.1 in polkadot-cli
  • 162c679 Do not block finality for "disabled" disputes (#3358) (#3385)
  • 2fe3145 move prdoc file to the release folder
  • f7cca1b [pallet_xcm] Forgotten migration to XCMv4 + added try-state to the `pallet_...
  • 97df9dd Fixup backing group computation time (#3170) (#3183)
  • 08cc7fe move prdocs to the release folder
  • 6f46a49 Bump spec_version
  • bb7479f Bump crate versions in: cumulus/polkadot-parachain/Cargo.toml
  • 75b67c5 Bump node version to 1.7.0 in polkadot-cli
  • Additional commits viewable in compare view

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 <dependency name> 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)

Bumps [frame-system](https://github.com/paritytech/polkadot-sdk) from polkadot-v1.6.0 to polkadot-v1.7.1.
- [Release notes](https://github.com/paritytech/polkadot-sdk/releases)
- [Changelog](https://github.com/paritytech/polkadot-sdk/blob/master/docs/RELEASE.md)
- [Commits](paritytech/polkadot-sdk@481165d...70e569d)

---
updated-dependencies:
- dependency-name: frame-system
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Feb 20, 2024
Copy link
Contributor Author

dependabot bot commented on behalf of github Feb 20, 2024

Looks like frame-system is up-to-date now, so this is no longer needed.

@dependabot dependabot bot closed this Feb 20, 2024
@dependabot dependabot bot deleted the dependabot/cargo/development/frame-system-polkadot-v1.7.1 branch February 20, 2024 11:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants