DSE 6.8.40 release notes #121
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
thobe
approved these changes
Nov 6, 2023
thobe
suggested changes
Nov 6, 2023
DSE_6.8_Release_Notes.md
Outdated
| @@ -2,6 +2,30 @@ | |||
| DSE 6.8.x is compatible with Apache Cassandra™ 3.11 and adds additional production-certified changes, if any. | |||
| Components that are indicated with an asterisk (*) (if any) are known to be updated since the prior patch version. | |||
|
|
|||
| # Release notes for 6.8.40 | |||
| 9 November 2023 | |||
szymon-miezal
force-pushed
the
dse-6.8.40-release
branch
from
6ddb4b3 to
7375111
Compare
szymon-miezal
force-pushed
the
dse-6.8.40-release
branch
from
7375111 to
eaf6869
Compare
szymon-miezal
force-pushed
the
dse-6.8.40-release
branch
from
eaf6869 to
46f8425
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.