Skip to content

Consider using cargo-semver-checks #318

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

Closed
brycx opened this issue Feb 14, 2023 · 0 comments · Fixed by #459
Closed

Consider using cargo-semver-checks #318

brycx opened this issue Feb 14, 2023 · 0 comments · Fixed by #459
Labels
good first issue Good for newcomers testing All testing, except for fuzzing related

Comments

@brycx
Copy link
Member

brycx commented Feb 14, 2023

We should consider using cargo-semver-checks as part of our CI, so we don't accidentally introduce breaking changes.

@brycx brycx added good first issue Good for newcomers testing All testing, except for fuzzing related labels Feb 14, 2023
@brycx brycx added this to the 0.17.4 milestone Feb 14, 2023
@brycx brycx removed this from the 0.17.4 milestone Mar 4, 2023
@brycx brycx closed this as completed in #459 Apr 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers testing All testing, except for fuzzing related
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant