-
Notifications
You must be signed in to change notification settings - Fork 1.9k
[branch-52] Prepare 52.0.0 release version number and changelog #19661
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: branch-52
Are you sure you want to change the base?
Conversation
c11ed74 to
8a43831
Compare
8a43831 to
bb9f8ed
Compare
| tool: cargo-audit | ||
| - name: Run audit check | ||
| run: cargo audit | ||
| run: cargo audit --ignore RUSTSEC-2026-0001 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like the issue from upstream isn't easy to resolve. I added the ignore here to not block CI.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is probably worth adding a comments about why we need this -- specifically we can copy the comments from
# RUSTSEC-2026-0001: https://rustsec.org/advisories/RUSTSEC-2026-0001.html
# underlying rkyv is patched, but rustsec database not yet updated
# Can remove when this is merged: https://github.com/rustsec/advisory-db/pull/2565
alamb
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @xudong963
| 1 hsiang-c | ||
| 1 r1b | ||
| 1 rin | ||
| 1 xavlee |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
119 contributors by my count 🍠
Which issue does this PR close?
52.0.0(Dec 2025 / Jan 2026) #18566Rationale for this change
What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?