gador/nixpkgs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
847,044 Commits 9 Branches 0 Tags
3ebaea3e615ee6e8b0ddd1989076302dbfc5e7e8
Commit Graph
847044 Commits
This Branch
This Branch
All Branches
Author SHA1 Message Date
Philip TaronandGitHub 3ebaea3e61 maintainers: donteatoreo -> FlameFlag, treewide: donteatoreo -> FlameFlag (#435327) 2025-08-20 10:25:45 -07:00
nixpkgs-merge-bot[bot]GitHubcarlossless
 		8bd286875e e1s: 1.0.49 -> 1.0.50 (#435287) 
Co-authored-by: carlossless <contact@carlossless.io>
 2025-08-20 17:20:02 +00:00
FlameFlag 31e7a5516e treewide: donteatoreo -> FlameFlag 2025-08-20 20:17:00 +03:00
tomberekandGitHub af935b61f3 souffle: 2.4.1 -> 2.5 (#392748) 2025-08-20 13:03:58 -04:00
FlameFlag 7a07eec4eb maintainers: donteatoreo -> FlameFlag 2025-08-20 20:01:36 +03:00
dotlambdaandGitHub b57c89c378 python3Packages.libpyfoscamcgi: 0.0.6 -> 0.0.7 (#435245) 2025-08-20 10:00:45 -07:00
dotlambdaandGitHub c0b9d6149f immich: 1.138.0 -> 1.138.1 (#435036) 2025-08-20 09:59:51 -07:00
Wolfgang WaltherandGitHub d20a6a3f8f ci/github-script/prepare: move more steps from workflow (#435302) 2025-08-20 16:57:23 +00:00
Wolfgang WaltherandGitHub c8aea5f2e9 workflows: use cachix consistently (#435294) 2025-08-20 16:54:01 +00:00
Wolfgang Walther f01b6b4754 actions/checkout: remove unused input types 
The two as-at inputs, were not boolean anymore, but GHA didn't complain.
Input types are actually not a thing for composite actions - they are
only documented for callable workflows.
 2025-08-20 18:52:20 +02:00
Matteo PaciniandGitHub 1236127220 tor-browser: 14.5.5 -> 14.5.6 (#435144) 2025-08-20 17:50:08 +01:00
nixpkgs-merge-bot[bot]GitHubymstnt
 		16263d3cbe hifile: 0.9.12.0 -> 0.9.12.1 (#435286) 
Co-authored-by: ymstnt <ymstnt@users.noreply.github.com>
 2025-08-20 16:43:22 +00:00
Scott PruttonandAustin Seipp 60fd662d96 buck2: unstable-2025-05-06 -> unstable-2025-08-15 2025-08-20 11:38:55 -05:00
Matt SturgeonandGitHub 1c53d4b27c nexusmods-app: 0.14.3 -> 0.15.2 (#433654) 2025-08-20 17:36:05 +01:00
tomberekandGitHub 3104ac9d58 teleport_18: init at 18.1.1 (#411095) 2025-08-20 12:34:15 -04:00
David McFarlandandGitHub d02f749240 dotnet: fix problems with --runtime flags (#432571) 2025-08-20 13:28:25 -03:00
tomberekandGitHub c3fc1fe6d8 papertrail: switch to pname (#411456) 2025-08-20 12:17:59 -04:00
Martin WeineltandGitHub a2c91dce28 Firefox: 141.0.3 -> 142.0; 140.1.0esr -> 140.2.0esr (#435118) 2025-08-20 18:17:13 +02:00
Wolfgang Walther ac93865697 workflows/build: prevent pushing tarball to cachix 
By definition the tarball changes on every commit, so it makes no sense
to cache it - it will just waste disk space.
 2025-08-20 18:08:43 +02:00
Wolfgang Walther 795dd01e31 workflows/eval: add cachix 
At this stage, this only allows faster iteration when working on CI in
forks.
 2025-08-20 18:08:39 +02:00
Wolfgang Walther 4d996cfb2f ci/nixpkgs-vet: ignore .github/ and ci/ folders 
nixpkgs-vet doesn't care about our CI infrastructure, so ignoring these
files will lead to more cache hits when iterating on CI related PRs.
 2025-08-20 18:08:16 +02:00
Wolfgang Walther c4fa63da49 ci/nixpkgs-vet: memoize filesets 
Speeds up evaluation a bit, because `filtered head` doesn't need to be
evaluated 3x.
 2025-08-20 18:08:14 +02:00
Wolfgang Walther 6ee40e7931 workflows/lint: add cachix 
For PRs targeting a fast moving branch like master, it might not
actually help because the merge commit will still be different on each
run. But on slower moving branches or when testing in a fork, it can
speed things up.

Since each of these build results is only a few hundred bytes without
any dependencies, it has essentially no cost.

Not adding this to `treefmt`, because this looks at *all* the files in
the repo, so needs to re-run even when iterating on CI only.
 2025-08-20 18:08:06 +02:00
SandroandGitHub 94a713a931 nextcloud-notify_push: 1.1.0 -> 1.2.0 (#432043) 2025-08-20 18:07:27 +02:00
Wolfgang Walther 2400bdf0d4 workflows: never push source to cachix 
Pushing the source path to cachix is pointless, because the only source
we're using is Nixpkgs - and that will always be available already via
checkout. No need to ever substitute it, so no need to push it either.
 2025-08-20 18:06:30 +02:00
Wolfgang Walther 025424913f workflows: support cachix in forks 
This allows setting up a custom cachix cache in a contributor's fork.
That's most valuable when working on CI itself, testing and interating
in a fork. It's required when working on cachix related features
directly.
 2025-08-20 18:06:26 +02:00
tomberekandGitHub be54546c8f ruri: 3.8 -> 3.9.1 (#434384) 2025-08-20 12:05:16 -04:00
GrimmauldandGitHub 3a2ad3b3d9 librewolf-unwrapped: 141.0.3-1 -> 142.0.1 (#435116) 2025-08-20 16:05:05 +00:00
tomberekandGitHub 0bd8973aa6 wrkflw: 0.4.0 -> 0.7.0 (#434751) 2025-08-20 12:04:50 -04:00
tomberekandGitHub 547ec46298 drbd-utils: 9.27.0 -> 9.32.0 (#434202) 2025-08-20 12:03:45 -04:00
Wolfgang Walther f35d1cd2cc workflows/pr.prepare: specify cone mode explicitly 
This is the default, but who's supposed to know about that? Let's make
it explicit to be clear about the availability of files in `ci/`.
 2025-08-20 18:03:41 +02:00
StepBroBDandGitHub e4b5391521 raycast: 1.102.4 -> 1.102.5 (#435264) 2025-08-20 18:03:33 +02:00
tomberekandGitHub a95823c7aa otree: 0.3.0 → 0.5.0 (#435134) 2025-08-20 12:03:13 -04:00
tomberekandGitHub 4b6b83b74e czkawka: 9.0.0 -> 10.0.0 (#434860) 2025-08-20 12:01:01 -04:00
tomberekandGitHub bd505df1d6 hiera-eyaml: 3.0.0 -> 4.3.0 (#432907) 2025-08-20 11:59:49 -04:00
Wolfgang Walther f94fd64d53 ci/github-script/prepare: fix logging of branch classification 
Logging objects to stdout is not possible with `core.info`, so we
fallback to `console.log` instead. There's no functional difference for
these anyway.
 2025-08-20 17:59:27 +02:00
K900andGitHub 3cbbb1d71e mesa: 25.2.0 -> 25.2.1 (#435307) 2025-08-20 18:59:03 +03:00
tomberekandGitHub b83b595c68 vivaldi-ffmpeg-codecs: 119293 -> 120726 (#430504) 2025-08-20 11:58:41 -04:00
tomberekandGitHub 1c5f0a0f93 wivrn: 25.6.1 -> 25.8 (#432804) 2025-08-20 11:56:56 -04:00
R. RyantmandSandro Jäckel f9a47201ed nextcloud-notify_push: 1.1.0 -> 1.2.0 2025-08-20 17:54:33 +02:00
DominicandDominic Wrege b0b2036d2c librewolf-unwrapped: 141.0.3-1 -> 142.0.1 
firefox upstream release notes: https://www.firefox.com/en-US/firefox/142.0/releasenotes/

Security advisory: https://www.mozilla.org/en-US/security/advisories/mfsa2025-64/

Fixes:

    CVE-2025-9179
    CVE-2025-9180
    CVE-2025-9181
    (CVE-2025-9186 Android-only)
    CVE-2025-9182
    CVE-2025-9183
    CVE-2025-9187
    CVE-2025-9184
    CVE-2025-9185
 2025-08-20 17:47:34 +02:00
R. RyantmandFrancesco Gazzetta 4b1b963a0f ladybird: 0-unstable-2025-08-11 -> 0-unstable-2025-08-19 2025-08-20 15:47:28 +00:00
K900 aa6f03cf8d mesa: 25.2.0 -> 25.2.1 
Diff: https://gitlab.freedesktop.org/mesa/mesa/-/compare/mesa-25.2.0...mesa-25.2.1

Changelog: https://docs.mesa3d.org/relnotes/25.2.1.html
 2025-08-20 18:44:10 +03:00
Nikolay KorotkiyandGitHub bd9e4d1769 nchat: 5.8.4 -> 5.9.15 (#435209) 2025-08-20 19:24:29 +04:00
Wolfgang Walther 46a1b0a7bc ci/github-script/prepare: determine changed files 2025-08-20 17:18:36 +02:00
Wolfgang Walther 4220a03df8 ci/github-script/prepare: classify branches 2025-08-20 17:18:25 +02:00
Wolfgang Walther 9caf455441 ci/github-script/prepare: load systems 2025-08-20 17:17:12 +02:00
Wolfgang Walther 7ab632b30f actions/checkout: rename inconsistent pinned-from input 2025-08-20 17:17:07 +02:00
Wolfgang Walther b51e104439 actions/checkout: rename from actions/get-merge-commit 
This moves the logic to "check whether the PR can be merged and
determine the relevant commits" into the PR / prepare job directly -
since that's the only place where it is supposed to be used.

Because of the if condition in get-merge-commit, this logic was run
multiple times, for example in the lint workflow, where only one of
targetSha or mergedSha was provided as input. However, this input was
thrown away directly. This might not be a big problem, because this was
not expensive, so far. But with the next commit, this will become more
so.

This also separates the logic a bit cleaner - `prepare` figures out all
the parameters for the whole PR workflow, while `checkout` handles the
consistency around these checkouts.
 2025-08-20 17:17:04 +02:00
Wolfgang WaltherandGitHub c51fabfd6a workflows/codeowners: move into PR workflow (#434555) 2025-08-20 15:15:27 +00:00