The runtime stuff is probably quite concentrated to certain crates. We could for sure support to pass pallets to ignore or even say “ignore all pallets in this folder”. All that should be possible.
1 Like
Can someone create a doc somewhere to explain the publish process? How frequent does it got triggered? How to find the corresponding commit of a published version? How does the version bumping works?
The crate releases happen with every binary release which is every 3 weeks now I believe.
The releases are made by running GitHub - paritytech/parity-publish: A tool to manage publishing Parity's crates then doing some manual fixups by hand. Currently everything get’s major bumped but we’re working on doing this semantically.
This then gets pushed to the branch: release-crates-io-v$VERSION. You can see the crate versions there.
Any bug fixes then get pushed to that branch and crates are individually bumped as needed.
1 Like
Thanks for the info. Can we have this documented in the polkadot-sdk repo? And ensure the docs is always up-to-date.
1 Like
Built a tool to help tackle this issue. It modify any Cargo.toml to match an specific Polkadot SDK version. You can run it directly with cargo. Just announced here: Polkadot SDK Version Manager
2 Likes