DSE 6.9.23 release#278
Conversation
| | Netty/Buffer | 4.1.118.Final | [Apache-2.0](https://spdx.org/licenses/Apache-2.0.html) | | ||
| | Netty/Codec | 4.1.118.Final | [Apache-2.0](https://spdx.org/licenses/Apache-2.0.html) | | ||
| | Netty/Codec/HTTP | 4.1.118.Final | [Apache-2.0](https://spdx.org/licenses/Apache-2.0.html) | | ||
| | Netty/Codec/HTTP2 | 4.1.118.Final | [Apache-2.0](https://spdx.org/licenses/Apache-2.0.html) | | ||
| | Netty/Common | 4.1.118.Final | [Apache-2.0](https://spdx.org/licenses/Apache-2.0.html) | | ||
| | Netty/Handler | 4.1.118.Final | [Apache-2.0](https://spdx.org/licenses/Apache-2.0.html) | | ||
| | Netty/Resolver | 4.1.118.Final | [Apache-2.0](https://spdx.org/licenses/Apache-2.0.html) | | ||
| | Netty/Transport | 4.1.118.Final | [Apache-2.0](https://spdx.org/licenses/Apache-2.0.html) | |
There was a problem hiding this comment.
I have read this list motivated by todays PSIRT email, I was curious what netty version is reported, it seems to be 4.1.118 while the RNs report it's 4.1.128 - https://github.com/datastax/release-notes/blob/master/DSE_6.9_Release_Notes.md#components-versions-for-dse-6922. I guess the former is wrong considering the repo definition says 4.1.128 as well. Now I started thinking how many other 3rd party versions are wrong.
There was a problem hiding this comment.
For the record 6.8 has wrong netty version as well: https://github.com/datastax/release-notes/blob/master/3rd-party-software/DSE_6.8.64_3rd_party_software.md so it's certainly nothing new.
|
Also the Mina ticket was not picked up by RN. I need to amend this and will ask for re-approval |
|
Yes you're right. I amended for the latest 6.8 and 6.9 versions. We can fix the rest later. |
szymon-miezal
left a comment
szymon-miezal
left a comment
There was a problem hiding this comment.
Thank you, especially for fixing the 6.8 3rd party list!
bereng
force-pushed
the
dse-6.9.23-release
branch
from
92ffd2c to
c962c2c
Compare
|
Squashed before merge |
3 participants
Release Notes Automation
If you name your pull-request as "Product x.y.z Release ...", after merging the
PR, a GitHub Action will automatically create a product version tag "product-x.y.z".
Supported product names are:
Version supports 3 sets or 4 sets of digits.