I.e. if you're releasing a package today, you probably don't have to worry about support.
We simply chose to mark Jest 27 as unsupported in this case, but it did cost some debugging time.