I believe fixing this would mean doing the following:
- reverting the change
- republishing a new
v11.0.3, which is the same as v11.0.1
- adding the change back in, except adding the readme update part, too
- publishing a breaking release as
v12.0.0
Ideally, we could avoid this work by just checking out v11.0.1 and publishing that tag as v11.0.3, but I'm not sure if that works or not.
Originally posted by @JordanMartinez in #34 (comment)
I believe fixing this would mean doing the following:
v11.0.3, which is the same asv11.0.1v12.0.0Ideally, we could avoid this work by just checking out
v11.0.1and publishing that tag asv11.0.3, but I'm not sure if that works or not.Originally posted by @JordanMartinez in #34 (comment)