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: add release ci #66

Merged
merged 2 commits into from
Oct 29, 2024
Merged

chore: add release ci #66

merged 2 commits into from
Oct 29, 2024

Conversation

arriqaaq
Copy link
Contributor

This PR implements an automated release process. The workflow is triggered by pull requests targeting branches matching the release/* pattern.

Workflow Steps

  1. Extract Version: The version is extracted from the branch name (formatted as release/{version}) and validated against the version specified in Cargo.toml. If they do not match, the workflow fails.
  2. Check Semver: The workflow includes a step to check if the versioning adheres to semantic versioning standards.
  3. Create and Push Tag: A tag is created for the release version, and it is pushed to the origin repository.
  4. Generate Changelog: A changelog is generated using the git-cliff-action, providing a summary of changes since the last release.
  5. Commit Changelog: If the changelog has changes, it is committed and pushed to the release branch.
  6. Run Tests: All tests are executed to ensure stability and correctness of the codebase.
  7. Publish Crate: The crate is published to the Cargo registry, using a secure token for authentication.
  8. Create GitHub Release: Finally, a GitHub release is created, linking to the changelog and tagging the release version.

@arriqaaq arriqaaq requested a review from gsserge October 29, 2024 01:54
@arriqaaq arriqaaq force-pushed the chore/release-changelog branch from 9aabdfe to 3b725b8 Compare October 29, 2024 09:28
@arriqaaq arriqaaq merged commit 80bff43 into main Oct 29, 2024
2 checks passed
@arriqaaq arriqaaq deleted the chore/release-changelog branch October 29, 2024 10:48
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.

2 participants