Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automate a bit more releasing a version of this crate #1365

Closed
tomaka opened this issue Jan 2, 2020 · 2 comments
Closed

Automate a bit more releasing a version of this crate #1365

tomaka opened this issue Jan 2, 2020 · 2 comments

Comments

@tomaka
Copy link
Member

tomaka commented Jan 2, 2020

Releasing a new version of libp2p is very painful. One has to bump the version of every crate in all the Cargo.tomls, then publish packages one by one in the correct order (as they depend on each other).

Additionally, since there are cyclic dependencies within dev-dependencies, one has to actually tweak the Cargo.tomls right before publishing to remove dev-dependencies, and use cargo publish --allow-dirty.

The fact that this is so painful makes it really annoying to release hotfixes for example.

@tomaka tomaka changed the title Automate the release process a bit more Automate a bit more releasing a version of this crate Jan 2, 2020
@LegNeato
Copy link

LegNeato commented Jan 7, 2020

We have similar constraints to the first requirement in https://github.com/graphql-rust/juniper if you want to see how we solved it.

@thomaseizinger
Copy link
Contributor

Closing in favor of #2902.

@thomaseizinger thomaseizinger closed this as not planned Won't fix, can't repro, duplicate, stale Mar 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants