Skip to content

chore: merge main into next#2060

Open
Mirko-von-Leipzig wants to merge 33 commits intonextfrom
mirko/merge-maoin
Open

chore: merge main into next#2060
Mirko-von-Leipzig wants to merge 33 commits intonextfrom
mirko/merge-maoin

Conversation

@Mirko-von-Leipzig
Copy link
Copy Markdown
Collaborator

No description provided.

Mirko-von-Leipzig and others added 29 commits April 22, 2026 16:29
Co-authored-by: Mirko <48352201+Mirko-von-Leipzig@users.noreply.github.com>
Co-authored-by: Bobbin Threadbare <43513081+bobbinth@users.noreply.github.com>
Co-authored-by: Mirko <48352201+Mirko-von-Leipzig@users.noreply.github.com>
Co-authored-by: Mirko <48352201+Mirko-von-Leipzig@users.noreply.github.com>
…scanning (#2028)

Co-authored-by: Mirko <48352201+Mirko-von-Leipzig@users.noreply.github.com>
Co-authored-by: KOVACS Krisztian <krisztian.k@miden.team>
Co-authored-by: Mirko <48352201+Mirko-von-Leipzig@users.noreply.github.com>
@Mirko-von-Leipzig Mirko-von-Leipzig added the no changelog This PR does not require an entry in the `CHANGELOG.md` file label May 7, 2026
@Mirko-von-Leipzig Mirko-von-Leipzig force-pushed the mirko/merge-maoin branch 3 times, most recently from d29619e to 3be60c9 Compare May 7, 2026 10:57
@Mirko-von-Leipzig Mirko-von-Leipzig marked this pull request as ready for review May 7, 2026 11:06
@kkovaacs
Copy link
Copy Markdown
Contributor

kkovaacs commented May 7, 2026

BTW, I think we should includethe blocking task tracing span fix as well.

@Mirko-von-Leipzig
Copy link
Copy Markdown
Collaborator Author

BTW, I think we should includethe blocking task tracing span fix as well.

Eventually everything will come over, but I can pull that in as well.

Copy link
Copy Markdown
Collaborator

@sergerad sergerad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM but there are a lot of changes I haven't been across until now.

@Mirko-von-Leipzig
Copy link
Copy Markdown
Collaborator Author

LGTM but there are a lot of changes I haven't been across until now.

There's been a flurry of work on fixing the previous testnet performance issues, and then a bunch of CI churn that got invalidated by work on next.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no changelog This PR does not require an entry in the `CHANGELOG.md` file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants