You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's unlikely this will happen until #75 is closed given it's a known final backwards incompatible change I'd like to make, and there's no sense publishing a release labelled backwards compatible when there's a known change that needs making.
Development (both here and on jsonschema) has slowed quite a bit given I am no longer being sponsored to spend full-time on them, so I don't know when that will happen honestly.
My recommendation would be to simply use the package as is, I don't know why what version is used matters much, but a 1.0 (or really a 2025.X.Y) will come at some point whenever I do have either the motivation or hopefully funding to put a bunch more hours in.
Activity
Julian commentedon May 8, 2025
Hi.
It's unlikely this will happen until #75 is closed given it's a known final backwards incompatible change I'd like to make, and there's no sense publishing a release labelled backwards compatible when there's a known change that needs making.
Development (both here and on
jsonschema) has slowed quite a bit given I am no longer being sponsored to spend full-time on them, so I don't know when that will happen honestly.My recommendation would be to simply use the package as is, I don't know why what version is used matters much, but a 1.0 (or really a 2025.X.Y) will come at some point whenever I do have either the motivation or hopefully funding to put a bunch more hours in.