[WIP] Remove old categories in favor of the new taxonomy field#434
Open
[WIP] Remove old categories in favor of the new taxonomy field#434
Conversation
jonahadkins
approved these changes
Feb 4, 2026
82ba668 to
2b82e47
Compare
jenningsanderson
approved these changes
Feb 5, 2026
Collaborator
jenningsanderson
left a comment
There was a problem hiding this comment.
A major breaking change! Good to see.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Major change release plan
This is a major breaking change as it removes a field.
A. Expected release date for this MAJOR change
3/20206
C. Public documentation and messaging plan
TODO.
Description
Now that we have the new taxonomy field, remove the old categories field
Reference
List of relevant links to GitHub issues, PRs, and other documentation.
Testing
Test suite
Checklist
Checklist of tasks commonly-associated with schema pull requests. Please review the relevant checklists and ensure you do all the tasks that are required for the change you made.
Abut is not intended to test propertyA's validity, and you made a schema change that invalidates propertyAin that counterexample, fix the counterexample to align it with your schema change.Documentation website
Update the hyperlink below to put the pull request number in.
[Docs preview for this PR.](https://dfhx9f55j8eg5.cloudfront.net/pr/<PUT THE PR # HERE>)