Skip to content
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.

Sign up for GitHub

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

Jump to bottom

staging-next-24.11 iteration 4 - 2025-02-23 #384543

Open
wants to merge 140 commits into
base: release-24.11
Choose a base branch
from
Open

staging-next-24.11 iteration 4 - 2025-02-23 #384543

wants to merge 140 commits into from

Conversation

vcunat
Copy link
Member

@vcunat vcunat commented Feb 23, 2025

nixpkgs-ci bot and others added 30 commits January 21, 2025 00:16
@nixpkgs-ci
Merge staging-next-24.11 into staging-24.11
7bb0cf6
@nixpkgs-ci
Merge staging-next-24.11 into staging-24.11
cdc1e4b
@nixpkgs-ci
Merge staging-next-24.11 into staging-24.11
8d353da
@LeSuisse @github-actions
glibc: 2.40-36 -> 2.40-66
49f4abf 
Fixes CVE-2025-0395 / GLIBC-SA-2025-0001
https://sourceware.org/git/?p=glibc.git;a=blob;f=advisories/GLIBC-SA-2025-0001;h=45f8b8f181fa024611452518ca0147ede1b88c47;hb=d9dcfe766eb9adcf9b1143112b569ac34ea9a9e6
https://www.openwall.com/lists/oss-security/2025/01/22/4

(cherry picked from commit ca851b6)
@nixpkgs-ci
Merge staging-next-24.11 into staging-24.11
df4e535
@trofi @github-actions
libopenmpt: 0.7.12 -> 0.7.13
a4c7d01 
Changes: https://lib.openmpt.org/libopenmpt/2025/01/06/releases-0.7.13-0.6.22-0.5.36-0.4.48/
(cherry picked from commit 7571606)
@Ma27
Merge: [Backport staging-24.11] glibc: 2.40-36 -> 2.40-66 (#376245)
e868560
@nixpkgs-ci
Merge staging-next-24.11 into staging-24.11
2a69c67
@nixpkgs-ci
Merge staging-next-24.11 into staging-24.11
8669235
@nixpkgs-ci
Merge release-24.11 into staging-next-24.11
72f16f8
@nixpkgs-ci
Merge staging-next-24.11 into staging-24.11
a6e377d
@nixpkgs-ci
Merge release-24.11 into staging-next-24.11
9c1155a
@nixpkgs-ci
Merge staging-next-24.11 into staging-24.11
019ed68
@nixpkgs-ci
Merge release-24.11 into staging-next-24.11
81073f7
@nixpkgs-ci
Merge staging-next-24.11 into staging-24.11
51f6e55
@nixpkgs-ci
Merge release-24.11 into staging-next-24.11
7b72a72
@nixpkgs-ci
Merge staging-next-24.11 into staging-24.11
348a196
@aduh95 @github-actions
nodejs_20: 20.18.1 -> 20.18.2
338dc37 
(cherry picked from commit 0be1c4a)
@nixpkgs-ci
Merge release-24.11 into staging-next-24.11
c6fb19b
@nixpkgs-ci
Merge staging-next-24.11 into staging-24.11
0c52727
@OPNA2608
[Backport staging-24.11] libopenmpt: 0.7.12 -> 0.7.13 (#376478)
ffc39a8
@K900 @github-actions
qt6: 6.8.1 -> 6.8.2
86c0981 
(cherry picked from commit fd28cb8)
@K900
[Backport staging-24.11] [staging-next] qt6: 6.8.1 -> 6.8.2 (#378285)
8dec3c6
@wolfgangwalther
[Backport staging-24.11] nodejs_20: 20.18.1 -> 20.18.2 (#378145)
40ae8d5
@nixpkgs-ci
Merge release-24.11 into staging-next-24.11
1896180
@nixpkgs-ci
Merge staging-next-24.11 into staging-24.11
b6f7d33
@nixpkgs-ci
Merge release-24.11 into staging-next-24.11
4e75aaf
@nixpkgs-ci
Merge staging-next-24.11 into staging-24.11
a66dadc
@nixpkgs-ci
Merge release-24.11 into staging-next-24.11
acb3f84
@nixpkgs-ci
Merge staging-next-24.11 into staging-24.11
3481d1e
@vcunat vcunat added the 1.severity: security Issues which raise a security issue, or PRs that fix one label Feb 23, 2025
@vcunat vcunat changed the base branch from master to release-24.11 February 23, 2025 15:58
@github-actions github-actions bot added 6.topic: python 6.topic: rust 6.topic: TeX Issues regarding texlive and TeX in general 6.topic: dotnet Language: .NET 6.topic: continuous integration Affects continuous integration (CI) in Nixpkgs, including Ofborg and GitHub Actions 6.topic: golang 6.topic: vim 6.topic: nodejs 6.topic: tcl and removed 6.topic: rust 6.topic: TeX Issues regarding texlive and TeX in general 6.topic: dotnet Language: .NET 6.topic: continuous integration Affects continuous integration (CI) in Nixpkgs, including Ofborg and GitHub Actions labels Feb 23, 2025
@ofborg ofborg bot added 2.status: merge conflict This PR has merge conflicts with the target branch and removed 2.status: merge conflict This PR has merge conflicts with the target branch labels Feb 23, 2025
@vcunat
Copy link
Member Author

vcunat commented Feb 23, 2025

Oops. I hope I retargeted the PR fast enough.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
1.severity: security Issues which raise a security issue, or PRs that fix one 6.topic: golang 6.topic: nodejs 6.topic: python 6.topic: tcl 6.topic: vim 10.rebuild-darwin: 501+ 10.rebuild-darwin: 5001+ 10.rebuild-linux: 501+ 10.rebuild-linux: 5001+
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.