We used to be able to publish Substrate to crates.io and at some stage the process broke and remain broken as current. I don’t think I need to re-iterate the benefits of be able to publish Substrate to a package registry. Someone need to re-investigate the current status of the publish process, wh…

We kicked this off last week. The person working on it is currently creating a write up on how to tackle it. Will post more updates when I have more information.

Crates for Substrate as well as Polkadot and Cumulus are now live. The plan is to publish new crate versions every time we have a Polkadot node release. Currently we’re just bumping the major version of each crate on each release but we are working on having semver aware versioning at some point in…

Any updates about this regards the new polkadot-sdk repo? Is the new publish pipeline ready? What’s the release frequency? What’s the latest release? Release notes? Is it ready for downstream projects to use?

Re-echoing @xlc 's comments. Is the case that the crates.io versions will match the GitHub version? Wen Polkadot-v1.1.0?

[image] xlc: Any updates about this regards the new polkadot-sdk repo? Is the new publish pipeline ready? Yes, every release of the Parity Polkadot node is done together with a release of all crates to crates.io . [image] xlc: What’s the release frequency? Every 2 weeks. [image] xl…

All the crates seem to have their version number chosen at random. Is it possible to just have v1.1.0 on all of them. Literally No way to use them because of the different versions

This doesn’t work. Because you can overwrite old crate versions. So, we have to start with the old crate versions and bump them as we go. There could probably be introduced some kind of tooling that updates all of your crates to the latest version on crates.io .

If that’s the case, then maybe set all of them to the highest major version. So that this way, versions move in lockstep. I can tell you that different major versions will cause incompatibilities across crates.

In the future we don’t want to bump only the major versions. Bump only major, minor or patch depending on the changes. Then these versions will also not go in lockstep.

Publish Substrate to crates.io

Tech Talk

patricio March 11, 2024, 10:51am 46

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

Topic		Replies	Views
PSA: Parity is currently working on merging the Polkadot stack repositories into one single repository Ecosystem	28	3679	September 25, 2023
Polkadot Release Analysis v1.1.0 Ecosystem release-analysis	3	1299	October 3, 2023
Polkadot Release Analysis v1.13.0 Ecosystem release-analysis	0	357	June 18, 2024
Stabilizing Polkadot Ecosystem	33	3396	September 27, 2024
Polkadot Release Analysis v1.0.0 Ecosystem release-analysis	3	2116	September 12, 2023

Publish Substrate to crates.io

Related topics