Skip to content

ci: move to new release-plz release flow #3369

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.

Sign up for GitHub

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

Jump to bottom
Closed
antonbaliasnikov wants to merge 1 commit into from
Closed

ci: move to new release-plz release flow #3369

antonbaliasnikov wants to merge 1 commit into from

Conversation

@antonbaliasnikov
Copy link
Contributor

@antonbaliasnikov antonbaliasnikov commented Dec 9, 2024

What ❔

Draft of the new release flow using release-plz.

Why ❔

To publish crates to crates.io and unify release process.

Checklist

  • PR title corresponds to the body of PR (we generate changelog entries from PRs).
  • Tests for the changes have been added / updated.
  • Documentation comments have been added / updated.
  • Code has been formatted via zkstack dev fmt and zkstack dev lint.

@antonbaliasnikov antonbaliasnikov linked an issue Dec 9, 2024 that may be closed by this pull request
Automatic publishing on crates.io #3279
Open
@antonbaliasnikov
Copy link
Contributor Author

antonbaliasnikov commented Dec 12, 2024

Closing after discussion that binary crates should not be released to crates.io yet, because release-plz is not supporting git-only mode yet and always works through crates.io for now.

@antonbaliasnikov antonbaliasnikov deleted the aba-new-release-flow branch January 29, 2025 15:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Automatic publishing on crates.io

1 participant

@antonbaliasnikov