feat(crates-io): publish gstd and gear-wasm-builder

[clearloop]

Resolves #3500
Resolves #3528
Resolves #3131

• split crates-io-manager into parts
• update parity-wasm in pwasm-utils ( -> gear-pwasm-utils )
• publish gstd
• publish gear-wasm-builder

testing action: https://github.com/gear-tech/gear/actions/runs/6970605696/job/18968871282

@gear-tech/dev

[breathx]

why do we need publish it on each commit? that's meaningless. we must do it only on releases

[clearloop]

why do we need publish it on each commit? that's meaningless. we must do it only on releases

the version is not bumping but with commit hash https://crates.io/crates/actor-system-error/1.0.2-354d660.8, btw since we are bumping versions before release, we can not run publishing tests with CI ( because --dry-run requires all dependencies being published ), the overall logic is easy to be broken once we add more local dependencies to the to-be-published packages

[StackOverflowExcept1on]

I think we can remove it now (parity-wasm, wasm-instrument) and use the versions from crates.io:

gear/Cargo.toml

Lines 501 to 504 in 3a06def

	[patch.crates-io]
	parity-wasm = { version = "0.45.0", git = "https://github.com/gear-tech/parity-wasm", branch = "v0.45.0-sign-ext" }
	wasmi-validation = { version = "0.5.0", git = "https://github.com/gear-tech/wasmi", branch = "v0.13.2-sign-ext" }
	wasm-instrument = { version = "0.3.0", git = "https://github.com/gear-tech/wasm-instrument", branch = "v0.3.0-sign-ext" }

[breathx]

why do we need publish it on each commit? that's meaningless. we must do it only on releases

the version is not bumping but with commit hash https://crates.io/crates/actor-system-error/1.0.2-354d660.8, btw since we are bumping versions before release, we can not run publishing tests with CI ( because --dry-run requires all dependencies being published ), the overall logic is easy to be broken once we add more local dependencies to the to-be-published packages

So please write comment about it in each to-be-published crates toml. Also here's space to write some tooling that will check it.

We bump after releases so master always has greater version than last release. Also I couldn't find dry-run across repo.

[clearloop]

what about #3515 (comment)?

see the chat in our tg channel

[NikVolf]

@thecaralice care to take a look?

[thecaralice]

rust-lang/cargo#1169 has been open for eight years now and still doesn't even have a draft implementation PR, so I don't think it will be implemented anytime soon. However, the discussion mentions different solutions being:

• gitlab:torkleyy/cargo-publish-all
• pksunkara/cargo-workspaces
• crate-ci/cargo-release

The latter looks pretty promising.

Note: looks like cargo publish --dry-run does not check versions (rust-lang/cargo#1169 (comment))

[thecaralice]

What I dislike about this specific PR is that it doesn't have a single issue it addresses. I believe it should be split into several PRs:

• Add cargo publish workflow job for automatic publishing on tags
• Publish gstd and gear-wasm-builder
• Update dependencies in pwasm-utils
• Refactor crates.io manager (can questionably be merged with the first one)

[shamilsan]

👍

[clearloop]

• gitlab:torkleyy/cargo-publish-all
• pksunkara/cargo-workspaces
• crate-ci/cargo-release

these tools don't work for our situation, bcz we need to modify specified dependencies before publishing them https://github.com/gear-tech/gear/blob/cl/issue-3500/utils/crates-io/src/rename.rs

Note: looks like cargo publish --dry-run does not check versions (rust-lang/cargo#1169 (comment))

we are not using --dry-run now to check publishing since our version in git repo is always greater than the release version

• Add cargo publish workflow job for automatic publishing on tags

#3158

• Publish gstd and gear-wasm-builder
• Update dependencies in pwasm-utils

this is part of .2 and was doing outside of the gear repo

• Refactor crates.io manager (can questionably be merged with the first one)

crates-io-manager is not in production for now since there are still some packages needed to be published but not included in its logic

[NikVolf]

@breathx ?