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

chore: update release.toml config #1677

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

vmx
Copy link
Contributor

@vmx vmx commented Mar 9, 2023

This way releases can be made with the most recent version 0.25.5 of cargo-release. New major releases can be cut with simply running:

cargo release major --execute

Prior to this change fil-proofs-tooling wasn't tagged. With this change it's tagged just like any other crates. That adds more consistency. It still isn't published to crates.io as intended.

The consolidate-commits = false option makes sure that each crate gets its own tag with a commit message that contains its version number. Without this setting, it would only say "Release" without further information.

This way releases can be made with the most recent version 0.25.5 of
cargo-release. New major releases can be cut with simply running:

    cargo release major --execute

Prior to this change `fil-proofs-tooling` wasn't tagged. With this
change it's tagged just like any other crates. That adds more consistency.
It still isn't published to crates.io as intended.

The `consolidate-commits = false` option makes sure that each crate
gets its own tag with a commit message that contains its version number.
Without this setting, it would only say "Release" without further
information.
@vmx
Copy link
Contributor Author

vmx commented Mar 9, 2023

I should note that this PR preserves the current behaviour. Those newer versions of cargo-release make it possible to have a single tag/commit for everything. As we release all version at once we might even want that. I leave the decision to @cryptonemo.

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.

None yet

1 participant