Skip to content

ci: publish crates through crates_publish_automation - #239

Open
gab8i wants to merge 6 commits into
masterfrom
gab_release-automation
Open

gab8i wants to merge 6 commits into
masterfrom
gab_release-automation

Conversation

@gab8i

@gab8i gab8i commented Sep 16, 2026

Copy link
Copy Markdown

Moves publishing from manual cargo publish to paritytech/crates_publish_automation. Publishing a GitHub Release now packages the publishable crates, uploads them as an artifact, and dispatches the central publisher, which publishes whatever crates.io does not have yet.

@gab8i
gab8i marked this pull request as ready for review September 17, 2026 09:12
@gab8i
gab8i requested a review from a team as a code owner September 17, 2026 09:12
@gab8i
gab8i requested a review from skunert September 21, 2026 13:07
Comment thread test-support/keccak-hasher/Cargo.toml Resolved
Comment thread CONTRIBUTING.md
e.g. `git tag trie-db-v0.2.2` and push it with `git push origin trie-db-v0.2.2`
Crates are published by paritytech/crates_publish_automation as `parity-crate-owner`.

1. Merge a PR that bumps the version of each crate being released and of the

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: In litep2p Egor handled this as gitaction w version bump as well: paritytech/litep2p#599 probably could take some inspiration from that?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One difference is that for litep2p that is only one crate and one release right? Here we have multiple crates, which is a bit more shitty to handle via the GH interface. You would need to note down before which crate gets bumped to which version and then enter this on workflow triggering.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants