merge PRs from master to develop branch #2487
Merged
Conversation
This file contains 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
draft release v1.4.2-alpha
Draft release v1.4.3-alpha
Draft release v1.4.4-beta
Draft release v1.4.5
merge develop to master for several 4844 bug fix.
Draft release v1.4.6
Draft release v1.4.7
…2448) This PR adds a limit of 1000 to the "inner" topics in a filter-criteria Co-authored-by: Martin HS <[email protected]>
merge some PRs for v1.4.7(2nd)
buddh0
approved these changes
May 22, 2024
brilliant-lx
approved these changes
May 22, 2024
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.
Description
Some PRs were merged to master branch directly mainly for hard fork release, as we prefer not to include several risky PRs in hard fork release. PRs for v1.4.8 Haber release were not included in develop branch yet, this is to bring these PRs back to develop branch.
Rationale
NA
Example
NA
Changes
NA