It’s still in progress of release validation since there is no enough votes for the moments: https://lists.apache.org/thread/grgybp1m1mqx9rdy65czbh0wr1fz0ovg <https://lists.apache.org/thread/grgybp1m1mqx9rdy65czbh0wr1fz0ovg>
Once the release will be voted and approved, then it will be published and announced on the mailing list. It may take additional 1-2 days. — Alexey > On 3 Oct 2022, at 11:43, Varun Chopra via user <user@beam.apache.org> wrote: > > Classification: For internal use only > > Hi Team, > > Any confirmation on the 2.42.0 release? > > Please let us know I think its been 72 hours for RC1 also. > > Thanks, > Varun > > From: Evan Galpin <egal...@apache.org> > Sent: Thursday, September 29, 2022 2:15 AM > To: user@beam.apache.org > Subject: Re: [Question] Beam 2.42.0 Release Date Confirmation > > Hi there :-) > > You can follow the vote on the first release candidate for 2.42.0 here: > https://lists.apache.org/thread/ho2mvvgc253my1ovqmrxjpql8gvz0285 > <https://urldefense.com/v3/__https:/lists.apache.org/thread/ho2mvvgc253my1ovqmrxjpql8gvz0285__;!!Ox6YuIEURLHpS_c!cD31FLeSQ2bTm1jpO7C1f5nTZu_rVvb64P9HZX6Pvfh3WTdYhLADo2TXXE-Pg60zyrxwhka6Z6pXaJgC$> > > Thanks, > Evan > > On Tue, Sep 27, 2022 at 7:16 AM Varun Chopra via user <user@beam.apache.org > <mailto:user@beam.apache.org>> wrote: > Classification: Public > > Hi Team, > > We at Deutsche Bank are using Apache Beam SDK 2.41.0 and it has > Vulnerabilities of netty-codec under beam-vendor-grpcjar. > > We checked the Github fixes and seems like the code is fixed and merged. > > We wanted to understand when can we expect Apache Beam SDK 2.42.0 Version, so > that we can start using it. > > We have some urgent requirement for this fix, If you can provide some dates > that will help. > > Kind Regards, > Varun Chopra > > > > --- > This e-mail may contain confidential and/or privileged information. If you > are not the intended recipient (or have received this e-mail in error) please > notify the sender immediately and destroy this e-mail. Any unauthorized > copying, disclosure or distribution of the material in this e-mail is > strictly forbidden. > > Privacy of communications > In order to monitor compliance with legal and regulatory obligations and our > policies, procedures and compliance programs, we may review emails and > instant messages passing through our IT systems (including any personal data > and customer information they contain), and record telephone calls routed via > our telephone systems. We will only do so in accordance with local laws and > regulations. In some countries please refer to your local DB website for a > copy of our Privacy Policy. > > Please refer to https://db.com/disclosures <https://db.com/disclosures> for > additional EU corporate and regulatory disclosures. > > > --- > This e-mail may contain confidential and/or privileged information. If you > are not the intended recipient (or have received this e-mail in error) please > notify the sender immediately and destroy this e-mail. Any unauthorized > copying, disclosure or distribution of the material in this e-mail is > strictly forbidden. > > Privacy of communications > In order to monitor compliance with legal and regulatory obligations and our > policies, procedures and compliance programs, we may review emails and > instant messages passing through our IT systems (including any personal data > and customer information they contain), and record telephone calls routed via > our telephone systems. We will only do so in accordance with local laws and > regulations. In some countries please refer to your local DB website for a > copy of our Privacy Policy. > > Please refer to https://db.com/disclosures <https://db.com/disclosures> for > additional EU corporate and regulatory disclosures.
