Clean up old deprecated_references.yml files automatically #301
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What are you trying to accomplish?
Cleanup old deprecated references automatically.
What approach did you choose and why?
When running
update-todo
on an old set of packages, clean up olddeprecated_references.yml
files automatically becausepackage_todo.yml
will be dumped and used as the replacement.What should reviewers focus on?
I forgot to release the deprecation of update-deprecations, so once this is approved I will be shipping another version of 2.x that introduces (along with using update-todo instead of update-deprecations) this and the deprecations in preparation for 3.0s release.
Type of Change
Additional Release Notes
Include any notes here to include in the release description. For example, if you selected "breaking change" above, leave notes on how users can transition to this version.
If no additional notes are necessary, delete this section or leave it unchanged.
Checklist