It appears that node.js uses the GitHub releases list when searching for what version to update to, and quictls has tagged 3.0.9, but not "released" it. (perhaps I'm missing some critical information as to why that is, but I'll take a stab in the dark and ask here :-) )
Is it possible, or is there something blocking making the openssl-3.0.9-quic1 tag an official release?
Thanks for the effort to keep this library updated with upstream 🙏
I see the discussions in #120 and #114 and understand that you will only be tagging and not marking any as releases. Looks like Node's update script needs fixing now
It appears that node.js uses the GitHub
releases
list when searching for what version to update to, and quictls has tagged 3.0.9, but not "released" it. (perhaps I'm missing some critical information as to why that is, but I'll take a stab in the dark and ask here :-) )Is it possible, or is there something blocking making the
openssl-3.0.9-quic1
tag an official release?Thanks for the effort to keep this library updated with upstream 🙏