tree fdc9794103f1193db3356cbfaf345a9f75e1f81d
parent ba2c81932d3f4c8f6e7bfc384b64a97f725341ea
author Jacob MacDonald <jakemac@google.com> 1649957577 -0700
committer GitHub <noreply@github.com> 1649957577 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJiWFrJCRBK7hj4Ov3rIwAAhIcIAAiHBMg8Dnp/VaF5sUUfpH6i
 lbZUWA5znxZ4Saxca8IoJ7hV2QDX+my1UIUAf8iqKtCknnsHnhkppBmd3DOdrNJY
 6x9GTZ2xVtnM8PQ0/AAj9x0UsyS6utXW4j7YxwdqLCrNrR2M2qKQUXjdKTdu6DXE
 xXmrDiMly/VmzlvbVQzug0Z9ahBv6GL3m7cMQUk2Ut+0J3FFaBK1B1AfAIYswP7a
 z5sWm5EvJ4TkzfZMNSukQ7Gl+3OlukTeCy0WAVIvXpC6c5iZti8YcmbgI/MzryaI
 q/aiOD+GejZwiqtjY2mD6zFPgcyDaQK8cuU+vRIQD5JR0WVu2NhZQPjbiTxC5k4=
 =uR4Z
 -----END PGP SIGNATURE-----
 

drop new constants from test_api and usages from test_core, re-publish test_core (#1688)

It turns out test_core did rely on some changes in test_api that weren't documented in the changelog, I yanked version 0.4.12, and this will re-publish it as 0.4.13.

We don't want to do a release in test_api because flutter users won't pick up that version for a long time (on stable at least), so this removes the reliance on those new apis as well.