[requirements][releases][heat][mistral][murano] Requirements freeze exception for yaql
Hello, I have another exception request... A critical security issue[1] was discovered recently and we are updating yaql to fix the issue. The required change was already merged into yaql and I've proposed a new yaql release[2]. I'd like to request a requirement freeze exception to pull the fixed version into upper constraints for 2024.1. Please let me know if you have any concern. Thank you, Takashi [1] https://bugs.launchpad.net/yaql/+bug/2048114 [2] https://review.opendev.org/c/openstack/releases/+/913230 -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit
The diff looks ok for removing a feature. I don't like this type of change during freeze though. If we could somehow confirm that no other openstack project uses that codepath I'd be happy with this. On 24-03-15 01:15:46, Takashi Kajinami wrote:
Hello,
I have another exception request...
A critical security issue[1] was discovered recently and we are updating yaql to fix the issue. The required change was already merged into yaql and I've proposed a new yaql release[2].
I'd like to request a requirement freeze exception to pull the fixed version into upper constraints for 2024.1. Please let me know if you have any concern.
Thank you, Takashi
[1] https://bugs.launchpad.net/yaql/+bug/2048114 [2] https://review.opendev.org/c/openstack/releases/+/913230
-- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit
-- Matthew Thode
On 2024-03-14 14:28:37 -0500 (-0500), Matthew Thode wrote:
The diff looks ok for removing a feature. I don't like this type of change during freeze though. If we could somehow confirm that no other openstack project uses that codepath I'd be happy with this. [...]
According to codesearch, the only projects which import yaql at all are Heat and Mistral (also Murano but it's not going to be included in the upcoming 2024.1 release). Maintainers for the affected projects already weighed in favorably on the related bug report. -- Jeremy Stanley
participants (3)
-
Jeremy Stanley
-
Matthew Thode
-
Takashi Kajinami