Bump version 2 -> 3 for pallets?

[nuke-web3]

The devhub is updating everything to v3.0.0 and there are still some pallets that are v2.0.0 - what needs to be done to have them formally upgraded to 3.0.0? I see some pallets don't use FRAME v2 macros but are marked as v3 in substrate.

Specific examples that are still v2.0.0 :

• https://github.com/paritytech/substrate/blob/master/frame/node-authorization/Cargo.toml
  • (blocking this docs update)
• https://github.com/paritytech/substrate/blob/master/frame/example/Cargo.toml
• https://github.com/paritytech/substrate/blob/master/frame/example-parallel/Cargo.toml
• https://github.com/paritytech/substrate/blob/master/frame/example-offchain-worker/Cargo.toml

I know that publishing to crates.io is required for others to set the correct version as well.

[xlc]

I think semvar is used so major version bump only happens if there is breaking change.

But I can see this is going to be messy because every pallets will have different version number and unrelated to FRAME version...

[nuke-web3]

IMHO every major release should bump every dependency to the latest released version to keep the entire substrate library on the same base know-to-work version throughout the codebase. I was under the impression this was the strategy (breaking change or not). Otherwise you will have to manually upgrade each breaking change, instead of just bumping everything (and troubleshooting your breakages)

[bkchr]

The example pallets make no sense to bump. They are not published anyway.

node-authorization was missed 100% cc @gnunicorn

[nuke-web3]

examples are not published on crates.io - but for consistency in the whole of substrate, can we bump them to 3.0.0 to avoid confusion?

[andresilva]

❯ rg "^version = \"2.0.*\"" -g '!*.lock' --no-heading
bin/node-template/node/Cargo.toml:version = "2.0.0"
bin/node-template/pallets/template/Cargo.toml:version = "2.0.0"
bin/node-template/runtime/Cargo.toml:version = "2.0.0"
bin/node/testing/Cargo.toml:version = "2.0.0"
bin/node/executor/Cargo.toml:version = "2.0.0"
bin/node/rpc/Cargo.toml:version = "2.0.0"
bin/node/browser-testing/Cargo.toml:version = "2.0.0"
bin/utils/chain-spec-builder/Cargo.toml:version = "2.0.0"
bin/utils/subkey/Cargo.toml:version = "2.0.0"
bin/node/runtime/Cargo.toml:version = "2.0.1"
bin/node/primitives/Cargo.toml:version = "2.0.0"
frame/node-authorization/Cargo.toml:version = "2.0.0"
frame/example-offchain-worker/Cargo.toml:version = "2.0.1"
frame/example/Cargo.toml:version = "2.0.0"
frame/example-parallel/Cargo.toml:version = "2.0.1"
bin/node/rpc-client/Cargo.toml:version = "2.0.0"
bin/node/cli/Cargo.toml:version = "2.0.0"
primitives/arithmetic/fuzzer/Cargo.toml:version = "2.0.0"
primitives/npos-elections/fuzzer/Cargo.toml:version = "2.0.0-alpha.5"
primitives/test-primitives/Cargo.toml:version = "2.0.0"
client/service/test/Cargo.toml:version = "2.0.0"
test-utils/runtime/Cargo.toml:version = "2.0.0"
test-utils/runtime/client/Cargo.toml:version = "2.0.0"
primitives/application-crypto/test/Cargo.toml:version = "2.0.0"
test-utils/runtime/transaction-pool/Cargo.toml:version = "2.0.0"
primitives/api/test/Cargo.toml:version = "2.0.1"
client/executor/runtime-test/Cargo.toml:version = "2.0.0"
primitives/runtime-interface/test-wasm/Cargo.toml:version = "2.0.0"
primitives/runtime-interface/test/Cargo.toml:version = "2.0.0"
primitives/runtime-interface/test-wasm-deprecated/Cargo.toml:version = "2.0.0"
test-utils/client/Cargo.toml:version = "2.0.1"

[bkchr]

I don't see a reason why we should bump everything. Stuff that isn't released, shouldn't be bumped. That makes no sense. Than there is other stuff like the wasm-builder that has its complete own release schedule (which got bumped because of these "bump" all strategy). On longterm, we need to get rid off this "bump" all anyway, to have a proper release strategy.

[kianenigma]

I am waiting for the day in which pallets have their own individual release, version and changelog, and we use the crate version for migrations.

[bkchr]

Me as well :)

[stale]

Hey, is anyone still working on this? Due to the inactivity this issue has been automatically marked as stale. It will be closed if no further activity occurs. Thank you for your contributions.

[kianenigma]

These crates have not changed, and thus will not be bumped.