DSE 6.8.65 Release Notes#284
Merged
Merged
Conversation
annieden
reviewed
Jul 14, 2026
annieden
reviewed
Jul 14, 2026
annieden
reviewed
Jul 14, 2026
annieden
reviewed
Jul 14, 2026
annieden
approved these changes
Jul 14, 2026
annieden
left a comment
annieden
left a comment
Contributor
There was a problem hiding this comment.
Approving, as long as you merge the several edits I made - which, btw, match the edits done in 6.9.
janmast1o
force-pushed
the
dse-6.8.65-release
branch
from
July 17, 2026 15:47
15ca119 to
d6c4e0f
Compare
annieden
approved these changes
Jul 17, 2026
annieden
left a comment
annieden
left a comment
Contributor
There was a problem hiding this comment.
additional ticket add is fine. approving!
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.