Skip to content
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

Merged
merged 3 commits into from
Aug 29, 2022
Merged

Update the release checklist #1366

merged 3 commits into from
Aug 29, 2022

Conversation

HCastano
Copy link
Contributor

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.

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`
Copy link
Collaborator

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?

Copy link
Contributor Author

@HCastano HCastano Aug 26, 2022

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

Copy link
Collaborator

Choose a reason for hiding this comment

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

Lol #1412

Copy link
Collaborator

@cmichi cmichi left a 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>
@HCastano HCastano merged commit f508fc4 into master Aug 29, 2022
@HCastano HCastano deleted the hc-updated-release-checklist branch August 29, 2022 17:15
cmichi added a commit that referenced this pull request Aug 31, 2022
* 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>
xermicus pushed a commit that referenced this pull request Sep 8, 2022
* 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>
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants