Skip to content

Document process for breaking changes #69

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

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Admonish to wait on maintainers landing stuff
Co-authored-by: Josh Triplett <josh@joshtriplett.org>
  • Loading branch information
workingjubilee and joshtriplett authored Aug 27, 2024
commit 5322b01f37a545ed661c9a4c08df1549b723a766
2 changes: 1 addition & 1 deletion src/breaking-changes/summary.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ Running crater should be done if nontrivial breakage is expected, so the informa
available during the final comment period.

If the impact isn't too high, looping in maintainers of to-be-broken crates and submitting PRs
to fix them can be a valid strategy. However, this can only affect the crates in question, and
to fix them (and ensuring those PRs have been merged and released) can be a valid strategy. However, this can only affect the crates in question, and
it does not automatically affect their dependents. Binary dependents may have already locked-in
a different, older version.

Expand Down
Loading