-
Notifications
You must be signed in to change notification settings - Fork 451
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Update the release checklist #1366
Conversation
This simplies the release checklist a bit by using both `cargo-unleash` and `cargo-release`. `cargo-release` has been way more reliable for publishing the ink! workspace than `cargo-unleash`, but we still use `cargo-unleash` to clean up our `dev-dependencies`. In the future it would be cool to automate more of the release process, such as tag creation and publishing, through `cargo-release`.
With #1367 these shouldn't be required anymore.
- We cannot release with `dev-dependencies` due to some cyclic dependencies that | ||
exist. | ||
1. Do a dry run with `cargo release [level] -v --no-tag --no-push --allow-dirty` | ||
1. Do a dry run with `cargo release [level] -v --no-tag --no-push` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What values can [level]
have?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can find them as part of the cargo-release
documentation. I don't think it makes sense to have them here, but if you think it would be helpful I don't mind adding them
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lol #1412
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Co-authored-by: Michael Müller <mich@elmueller.net>
* Update the release checklist This simplies the release checklist a bit by using both `cargo-unleash` and `cargo-release`. `cargo-release` has been way more reliable for publishing the ink! workspace than `cargo-unleash`, but we still use `cargo-unleash` to clean up our `dev-dependencies`. In the future it would be cool to automate more of the release process, such as tag creation and publishing, through `cargo-release`. * Remove steps related to `dev-dependencies` With #1367 these shouldn't be required anymore. * Add missing punctuation Co-authored-by: Michael Müller <mich@elmueller.net> Co-authored-by: Michael Müller <mich@elmueller.net>
* Update the release checklist This simplies the release checklist a bit by using both `cargo-unleash` and `cargo-release`. `cargo-release` has been way more reliable for publishing the ink! workspace than `cargo-unleash`, but we still use `cargo-unleash` to clean up our `dev-dependencies`. In the future it would be cool to automate more of the release process, such as tag creation and publishing, through `cargo-release`. * Remove steps related to `dev-dependencies` With #1367 these shouldn't be required anymore. * Add missing punctuation Co-authored-by: Michael Müller <mich@elmueller.net> Co-authored-by: Michael Müller <mich@elmueller.net>
This simplies the release checklist a bit by using both
cargo-unleash
and
cargo-release
.cargo-release
has been way more reliable forpublishing the ink! workspace than
cargo-unleash
, but we still usecargo-unleash
to clean up ourdev-dependencies
.In the future it would be cool to automate more of the release process,
such as tag creation and publishing, through
cargo-release
.