I need a tag of something recent, but before this breaking change, so I can point my in-development projects to that tag until I can update all the dependencies. As far as I can tell, the last commit before this breaking change is: f166574fb86922e1b9012994277fdaa46780c57a
We should tag it with v3.4.1. Then current dev should have its version in pyproject.toml updated to 3.5.0 and then that commit can be tagged v3.5.0.
It's entirely possible that #135 doesn't actually break old code, I haven't tested, so maybe this isn't necessary.
135 should not introduce a breaking change, but it will log a warning that using the annotation method will be deprecated at some point in the future. But for now, there is still logic for handling settings and state specified via annotation.
IIUC, #135 breaks a bunch of things.
I need a tag of something recent, but before this breaking change, so I can point my in-development projects to that tag until I can update all the dependencies. As far as I can tell, the last commit before this breaking change is: f166574fb86922e1b9012994277fdaa46780c57a
We should tag it with
v3.4.1
. Then current dev should have its version in pyproject.toml updated to 3.5.0 and then that commit can be taggedv3.5.0
.It's entirely possible that #135 doesn't actually break old code, I haven't tested, so maybe this isn't necessary.