Make the node version independent of the crate version #1495
Conversation
|
The CI pipeline was cancelled due to failure one of the required jobs. |
There was a problem hiding this comment.
Qs: we will version manually now? Is there a context for this change?
Overall it looks really good - now we won't get a node/worker version mismatch between releases (during development). Workers should still get rebuilt on every commit so breakages should be rare, but we just won't enforce that, which is fine for most dev. So this addresses the discussion at #626 nicely.
| @@ -33,7 +33,7 @@ use tokio::{io, net::UnixStream, runtime::Runtime}; | |||
| /// spawning the desired worker. | |||
| #[macro_export] | |||
| macro_rules! decl_worker_main { | |||
| ($expected_command:expr, $entrypoint:expr, $worker_version:expr) => { | |||
| ($expected_command:expr, $entrypoint:expr, $worker_version:expr $(,)*) => { | |||
| /// | ||
| /// The worker binaries associated to the node binary should ensure that they are using the same | ||
| /// version as the main node that started them. | ||
| pub const NODE_VERSION: &'static str = "1.1.0"; |
There was a problem hiding this comment.
Why not env!("CARGO_PKG_VERSION")?
There was a problem hiding this comment.
I mean, okay, we don't want to use the commit hash in node version, but why the node version should be independent from the crate version in the first place?
There was a problem hiding this comment.
Because crates.io semver works differently to how we version our nodes.
|
If we're doing this, we can probably also remove
|
We already have done versioning manually (when we speak about the node version). The context is that crates.io semver is different to how we version our node. For now we will bump every major version of every crate for putting it onto crates.io, but the node version should not follow these bumps. |
|
@paritytech/release-engineering you will then need to change this |
Add logic to check if the `BUILD_RELEASE_VERSION` tag is available in docker registry, if not calculate the previous version to use as secondary image. This fix the issue in test using the `secondary image` and bumping the `NODE_VERSION`. (e.g #1495)
ghost
mentioned this pull request
No description provided.