Repository navigation
chore: sync released versions for 0.59.4 - #8379
Merged
Merged
Conversation
github-actions
Bot
added
releases-note/chore
Xuanwo
marked this pull request as ready for review
October 5, 2026 09:53
Xuanwo
requested review from
PsiACE,
Xuanwo,
Zheaoli,
messense,
oowl,
silver-ymz,
suyanhanx,
tisonkun and
xyjixyjixyji
as code owners
October 5, 2026 09:53
Xuanwo
approved these changes
Oct 5, 2026
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
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.
Which issue does this PR close?
Release follow-up for 0.59.4.
Rationale for this change
Bring the published package versions back to main while preserving newer versions and development changes.
What changes are included in this PR?
Synchronize the package inventory, generated dependency versions, lockfiles and changelog from v0.59.4 using the existing version tool.
This PR is created with GITHUB_TOKEN, which does not trigger pull-request CI.
After reviewing it, close and reopen it with a maintainer account (or push an
update) to trigger the required checks before merging.
Are there any user-facing changes?
No runtime behavior changes.
AI Usage Statement
None. Generated by the repository release workflow.