Plan for new release

[MelSumner]

A new release is requested by our security team, so I've volunteered to contribute.
As such, I'd like to document some planned steps to get us to a new release.
This plan might change as I collaborate with @benschwarz but feedback from others is also welcome of course.

• build project locally
• run tests locally
• 1 test fails, see what it needs to pass
• there are six type errors when I run npm run watch, should try to resolve those (first?)
• (maybe this is a new release point, just to get releases current)
• incrementally upgrade dependencies in a way that doesn't break existing approach
• (maybe this is the second release point)
• determine what API is being used that is deprecated, so it can be refactored (and add it to this list?)
• upgrade dependencies that are breaking changes (and perhaps are the ones with the new APIs)
• refactor deprecated API code to use replacement API
• ensure project builds
• ensure there are enough tests
• ensure tests pass
• (maybe this is the third release point, would be a major release)