Add a 6.1.4 section to the release notes #2851
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
|
Yes, add records for everything added since 6.1.3 that you aware of |
|
Hmm, CI failure may or may not be related to #2853 |
Numpsy
force-pushed
the
614relnotes
branch
2 times, most recently
from
b5d7147 to
085f4d7
Compare
|
@xperiandri Is it worth publishing 6.1.4 to get the pending fixes and updates out, and to get a more up to date base for the 'update to a newer .NET version' changes? |
|
I can publish, why not |
xperiandri
force-pushed
the
614relnotes
branch
from
b015cd8 to
e2dcf9d
Compare
|
Looks like I merged all your PRs. |
|
will do |
xperiandri
approved these changes
Oct 26, 2025
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.
Description
As discussed in #2845 (comment)
Should I add an entry for #2843 at the same time?