-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 The issue tagged in #1071902 [0] (as well as the issue tagged in that one [1]) seems to be closed with the latest release, so this does not exactly seems like a blocker. If anything, doesn't this close #1071902 itself?
As for #1068929, while it brings the event-listener dependency, that alone does not bring async-lock 3.0 comaptibility as I ubderstand it. I'm fine with the merge of the bugs, but am failing to see how they are the same. In either case, there does no seem to be a blocker anymore if I understand the situation correctly. Best, Ananthu [0] https://github.com/smol-rs/async-lock/issues/81 [1] https://github.com/smol-rs/event-listener/issues/123 -----BEGIN PGP SIGNATURE----- iQJEBAEBCAAuJxxBbmFudGh1IEMgViA8d2VlcGluZ2Nsb3duQGRpc3Jvb3Qub3Jn PgUCZmTK0gAKCRDu7UeebOz3B4GUD/wNbu7V+WIf3Witx49DYiX5MXPncx1b0Le+ OvjA2qiU15DpxZA06MZFqQtgkyCxbL8qInE3K8YTfdwG3TcFOkZS10uuENpqlVDV kunLZ/tVp0nAb7UpRDGUFBevo0wcXMvrXOUp7X5ruzlFl7sSa8kG5ONWsGmTABVT rHCxzVsqL51RXzSnDZigO9DtY+rVwAHvHgDKG2VpqxhHLZ9hseq7kwYaT+at1to7 o4IuaAc+J+FP9nhs5y4tui8xYvTede7JvHqQJ35hvDS2EYNwbD1XVQ7nUC0L1Rm8 YJHQ8kx05Gfp76vVyIxOcOwIUKEvMX5YqH+yf0qLRjR0fpnXmVkiQMC1KiV4QOuS B4RE8PQEW1y97T3/IIfl/sIeU0ME04TBtsTq91x075sUcERSYsrhRVPGm+FZ3USO H9Y5hyc+J5nCB8jBA602b2rVNqqeKnmkCZyw0V8cJLMRhu6oxCSIdtpdT0T4juHB aq8gIqe46qJZm38i/BG5BY47+s4LCN/+25wziK/xMYU5sCxWO2nN+qcyGmW+D5cV jjR6SoHeTetSfTrxV3pDFxU43+O+U28piXpw/mSxuXWu+8PenJoBVal8skz9C5ME swcSalEUkxA3xadNyWYz6gR5Ipk9syYaiFkK1J9AOL230R8u/ah9umzAmcJMoo3m /nDYSBFS4A== =b4br -----END PGP SIGNATURE-----
