about summary refs log tree commit diff
path: root/pkgs/applications/networking/browsers
AgeCommit message (Collapse)AuthorFilesLines
2024-01-23Merge pull request #282028 from r-ryantm/auto-update/polypaneThomas Gerbet1-2/+2
polypane: 17.0.0 -> 17.1.0
2024-01-22microsoft-edge: 120.0.2210.77 -> 120.0.2210.144R. Ryantm1-6/+6
2024-01-20Merge pull request #279047 from r-ryantm/auto-update/vivaldiWeijia Wang1-3/+3
vivaldi: 6.5.3206.48 -> 6.5.3206.50
2024-01-19polypane: 17.0.0 -> 17.1.0R. Ryantm1-2/+2
2024-01-19opera: 106.0.4998.19 -> 106.0.4998.52R. Ryantm1-2/+2
2024-01-19brave: 1.61.114 -> 1.61.120Sean Buckley1-2/+2
https://community.brave.com/t/release-channel-1-61-120/526928
2024-01-18ungoogled-chromium: 120.0.6099.216-1 -> 120.0.6099.224-1networkException1-5/+5
https://chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop_16.html This update includes 4 security fixes. Google is aware of reports that an exploit for CVE-2024-0519 exists in the wild. CVEs: CVE-2024-0517 CVE-2024-0518 CVE-2024-0519
2024-01-18chromium: 120.0.6099.216 -> 120.0.6099.224David Leung1-3/+3
https://chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop_16.html This update includes 4 security fix. CVEs: CVE-2024-0517 CVE-2024-0518 CVE-2024-0519
2024-01-17lagrange-tui: 1.17.5 -> 1.17.6R. Ryantm1-2/+2
2024-01-14librewolf-unwrapped: 121.0-1 -> 121.0.1-1squalus1-5/+5
2024-01-12firefox: set meta.mainProgram to launcherName in wrapperMatthew_Cash1-0/+1
After #235912 changed the binary name for some Firefox packages, the meta.mainProgram value was no longer accurate and commands such as nix run nixpkgs#firefox-devedition failed because /bin/firefox was executed instead of /bin/firefox-devedition. This sets meta.mainProgram to launcherName, which contains the nameSuffix set in #235912, instead of inheriting the unwrapped package's mainProgram, which is always firefox with no suffix.
2024-01-11ungoogled-chromium: 120.0.6099.199-1 -> 120.0.6099.216-1networkException1-5/+5
https://chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop_9.html This update includes 1 security fix. CVEs: CVE-2024-0333
2024-01-10firefox-bin-uwnrapped: 121.0 -> 121.0.1Martin Weinelt1-409/+409
https://www.mozilla.org/en-US/firefox/121.0.1/releasenotes/
2024-01-10firefox-unwrapped: 121.0 -> 121.0.1Martin Weinelt1-2/+2
https://www.mozilla.org/en-US/firefox/121.0.1/releasenotes/
2024-01-10chromium: 120.0.6099.199 -> 120.0.6099.216emilylange1-3/+3
https://chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop_9.html This update includes 1 security fix. CVEs: CVE-2024-0333
2024-01-06vivaldi: 6.5.3206.48 -> 6.5.3206.50R. Ryantm1-3/+3
2024-01-05palemoon-bin: 32.5.1 -> 32.5.2OPNA26081-3/+3
2024-01-05Merge pull request #278603 from emilylange/chromiumEmily5-46/+57
{ungoogled-,}chromium: 120.0.6099.129 -> 120.0.6099.199, improve and move `recompressTarball`
2024-01-05ungoogled-chromium: 120.0.6099.129-1 -> 120.0.6099.199-1networkException1-5/+5
https://chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop.html This update includes 6 security fixes. CVEs: CVE-2024-0222 CVE-2024-0223 CVE-2024-0224 CVE-2024-0225
2024-01-05Merge pull request #275459 from emilylange/chromium-drop-inactive-maintainersWeijia Wang2-17/+9
chromium: drop inactive maintainers, CODEOWNERS: init chromium
2024-01-05brave: 1.61.109 -> 1.61.114Sean Buckley1-2/+2
https://community.brave.com/t/release-channel-1-61-114/524569
2024-01-04chromium: 120.0.6099.129 -> 120.0.6099.199emilylange1-3/+3
https://chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop.html This update includes 6 security fixes. CVEs: CVE-2024-0222 CVE-2024-0223 CVE-2024-0224 CVE-2024-0225
2024-01-04chromium: improve and move `recompressTarball`emilylange5-40/+51
Recap: We need that (arguably stupid) helper function/drv because the chromium tarball is big -- and is likely to increase even more in the future. So big, that we eventually exceeded hydra.nixos.org's max-output-limit (3G). Instead of raising global hydra's limit, it was decided that we recompress the tarball after deleting unused vendored files from it. I spent a lot of time on a version/prototype that does everything (downloading, decompression, tar extraction, deleting unused files, reproducible tar recreation and finally recompression) via stdin but eventually had to scratch that. GNU tar does not allow to create a tarball just from stdin, nixpkgs' stdenv isn't built with stdin/stdout/pipes in mind, and things a lot of other things I probably already forgot. Nonetheless, this version improves multiple things: - No more `mv` (used to be multiple, not just ours, since fetchzip had some as well) - No more `rm` to get rid of the extracted files before recompressing. Instead, we simply don't extract them in the first place (thanks to tar's --exlude). - No more "no space left" that happened due to `downloadToTemp = true;`. - Multithreaded xz decompression, since that commit is still in staging-next. We cannot use stdenv's unpackFile() because that does not allow us to specify the needed --exclude (and --strip-components=1 if we don't want to rely on glob matching). The hash changed because we now have a static base directory ("source") in the tarball, instead of whatever upstream provided us with (e.g. "chromium-120.0.6099.129").
2024-01-03Merge pull request #275079 from r-ryantm/auto-update/polypaneWeijia Wang1-2/+2
polypane: 16.0.0 -> 17.0.0
2024-01-03Merge pull request #274967 from r-ryantm/auto-update/operaWeijia Wang1-2/+2
opera: 105.0.4970.21 -> 106.0.4998.19
2024-01-02Merge pull request #274863 from yu-re-ka/chromium-llvm17Emily3-25/+3
chromium: use llvm 17
2024-01-02Merge pull request #273872 from rhysmdnz/edge-120Thomas Gerbet2-17/+10
microsoft-edge: 119.0.2151.72 -> 120.0.2210.61
2024-01-01Merge pull request #277805 from r-ryantm/auto-update/vivaldiNick Cao1-3/+3
vivaldi: 6.5.3206.39 -> 6.5.3206.48
2023-12-30vivaldi: 6.5.3206.39 -> 6.5.3206.48R. Ryantm1-3/+3
2023-12-30widevine-cdm: 4.10.2557.0 -> 4.10.2710.0R. Ryantm1-2/+2
2023-12-30chromium: remove maintainer handles from README.md, mention electronemilylange1-15/+7
Specifically the maintainers section is quite outdated and prone to get out of sync with whatever primary data we have (mostly meta.maintainers) in each derivation. In an attempt to lower the risk of ending up out of sync again, we simply remove the maintainer handles. Also adds a mention for the newly from source built electron variant, as almost everything except `upstream-info.nix` bumps will trigger electron rebuilds as well. And lastly, removes mentions of `chromium{Beta,Dev}` and the accompanying `google-chrome-{beta,dev}, that have been removed a few months ago. I might look into reworking bigger parts of the README.md in the future, but this honestly isn't that high of a priority for me for now.
2023-12-28opera: 105.0.4970.21 -> 106.0.4998.19R. Ryantm1-2/+2
2023-12-26mullvad-browser: 13.0.6 -> 13.0.7Felix Schröter1-2/+2
https://github.com/mullvad/mullvad-browser/releases/tag/13.0.7
2023-12-26tor-browser: 13.0.6 -> 13.0.8Felix Schröter1-3/+3
https://blog.torproject.org/new-release-tor-browser-1307/ https://blog.torproject.org/new-release-tor-browser-1308/
2023-12-24librewolf-unwrapped: 120.0.1-1 -> 121.0-1squalus1-7/+7
2023-12-24Merge pull request #275386 from dr460nf1r3/masterEmily1-2/+2
floorp: 11.6.1 -> 11.7.1
2023-12-23brave: set meta.mainProgramsg-qwt1-0/+1
2023-12-23Merge pull request #275875 from buckley310/2023-12-21-braveThomas Gerbet1-3/+3
brave: 1.61.101 -> 1.61.109
2023-12-22ungoogled-chromium: 120.0.6099.109-1 -> 120.0.6099.129-1networkException1-5/+5
https://chromereleases.googleblog.com/2023/12/stable-channel-update-for-desktop_20.html This update includes 1 security fix. Google is aware that an exploit for CVE-2023-7024 exists in the wild. CVEs: CVE-2023-7024
2023-12-22chromium: 120.0.6099.109 -> 120.0.6099.129networkException1-3/+3
https://chromereleases.googleblog.com/2023/12/stable-channel-update-for-desktop_20.html This update includes 1 security fix. Google is aware that an exploit for CVE-2023-7024 exists in the wild. CVEs: CVE-2023-7024
2023-12-22chromedriver: 120.0.6099.71 -> 120.0.6099.109networkException1-4/+4
2023-12-21floorp: 11.6.1 -> 11.7.1Nico Jensch1-2/+2
2023-12-21brave: 1.61.101 -> 1.61.109Sean Buckley1-2/+2
https://community.brave.com/t/release-channel-1-61-109/522518
2023-12-21brave: add buckley310 to maintainersSean Buckley1-1/+1
2023-12-19firefox-esr-unwrapped: 115.5.0esr -> 115.6.0esrYureka1-2/+2
https://www.mozilla.org/en-US/firefox/115.6.0/releasenotes/ https://www.mozilla.org/en-US/security/advisories/mfsa2023-54/ Fixes CVE-2023-6856 Fixes CVE-2023-6857 Fixes CVE-2023-6858 Fixes CVE-2023-6859 Fixes CVE-2023-6860 Fixes CVE-2023-6861 Fixes CVE-2023-6862 Fixes CVE-2023-6863 Fixes CVE-2023-6864 Fixes CVE-2023-6865 Fixes CVE-2023-6867
2023-12-19firefox-unwrapped: 120.0.1 -> 121.0Yureka1-2/+2
https://www.mozilla.org/en-US/firefox/121.0/releasenotes/ https://www.mozilla.org/en-US/security/advisories/mfsa2023-56/ Fixes CVE-2023-6135 Fixes CVE-2023-6856 Fixes CVE-2023-6857 Fixes CVE-2023-6858 Fixes CVE-2023-6859 Fixes CVE-2023-6860 Fixes CVE-2023-6861 Fixes CVE-2023-6863 Fixes CVE-2023-6864 Fixes CVE-2023-6865 Fixes CVE-2023-6866 Fixes CVE-2023-6867 Fixes CVE-2023-6868 Fixes CVE-2023-6869 Fixes CVE-2023-6870 Fixes CVE-2023-6871 Fixes CVE-2023-6872 Fixes CVE-2023-6873
2023-12-19firefox-bin-unwrapped: 120.0.1 -> 121.0Yureka1-409/+409
https://www.mozilla.org/en-US/firefox/121.0/releasenotes/ https://www.mozilla.org/en-US/security/advisories/mfsa2023-56/ Fixes CVE-2023-6135 Fixes CVE-2023-6856 Fixes CVE-2023-6857 Fixes CVE-2023-6858 Fixes CVE-2023-6859 Fixes CVE-2023-6860 Fixes CVE-2023-6861 Fixes CVE-2023-6863 Fixes CVE-2023-6864 Fixes CVE-2023-6865 Fixes CVE-2023-6866 Fixes CVE-2023-6867 Fixes CVE-2023-6868 Fixes CVE-2023-6869 Fixes CVE-2023-6870 Fixes CVE-2023-6871 Fixes CVE-2023-6872 Fixes CVE-2023-6873
2023-12-19chromium: drop inactive maintainersemilylange1-2/+2
Our ./maintainers/README.md has a section titled "How to lose maintainer status", which describes an "inactivity measure": Maintainers how haven't reacted to "package-related notifications" for more than 3 months can be removed. All those 4 maintainers that are getting dropped as part of this commit haven't responded to any such notifications (mostly review pings) for at least 3 months.
2023-12-18Merge pull request #274386 from reedrw/chromium-disable-libpng-patchEmily1-1/+1
chromium: never use libpng-apng patch
2023-12-18microsoft-edge: 119.0.2151.72 -> 120.0.2210.77Rhys Davies2-17/+10
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-08-14 05:19:20 +0000