If we aren't able to update to a config-rs with the fix for #464 we may need to temporarily fork the crate on crates.io, which would be quite undesirable. Our workaround for #464 has a poor impact on the config format we accept, so our internal target for removing that workaround, that we set about a month ago, was to fix this for our own next release, which is due at roughly the end of November.
So ideally we'd be able to pick up a new config-rs 0.13.x in the next week or so.
ijackson
commented
7 months ago
Hi. Might it be possible to do a 0.13.x point release?
In the Arti project we are blocked on #464 (our ticket https://gitlab.torproject.org/tpo/core/arti/-/issues/1058) which was fixed in config-rs mainline in #465, backported to 0.13.x in #486.
If we aren't able to update to a config-rs with the fix for #464 we may need to temporarily fork the crate on crates.io, which would be quite undesirable. Our workaround for #464 has a poor impact on the config format we accept, so our internal target for removing that workaround, that we set about a month ago, was to fix this for our own next release, which is due at roughly the end of November.
So ideally we'd be able to pick up a new config-rs 0.13.x in the next week or so.
Thanks for your attention.