github-actions[bot]
149a81c88d
Merge master into staging-next
2021-03-10 00:39:07 +00:00
Michael Weiss
1868ac1d21
chromiumDev: 90.0.4430.11 -> 90.0.4430.19
2021-03-09 21:36:12 +01:00
github-actions[bot]
3db2dee35f
Merge master into staging-next
2021-03-09 00:39:09 +00:00
Nikolay Korotkiy
a96be025a1
lagrange: 1.1.4 → 1.2.2
2021-03-08 21:46:55 +03:00
Frederik Rietdijk
277d488026
Merge staging into staging-next
2021-03-08 19:20:18 +01:00
Bernardo Meurer
e52507aeac
Merge pull request #115314 from viric/firefox-i686-linux
...
Allow firefox building in 32-bit systems
2021-03-08 04:31:07 +00:00
Sandro
9be5456c66
Merge pull request #115352 from OPNA2608/update/palemoon-29.1.0/21.05
...
palemoon: 29.0.1 -> 29.1.0
2021-03-07 21:49:08 +01:00
Lluís Batlle i Rossell
d2af381b40
firefox: build in 32-bit systems
...
Disabling "-g" and LTO so there aren't memory problems.
2021-03-07 19:37:15 +01:00
Sandro
00783f3f04
Merge pull request #115029 from buckley310/brave
...
brave: 1.20.110 -> 1.21.73
2021-03-07 18:22:41 +01:00
OPNA2608
2ef5683cd9
palemoon: 29.0.1 -> 29.1.0
2021-03-07 15:15:49 +01:00
github-actions[bot]
dcea8212b5
Merge staging-next into staging
2021-03-07 12:20:40 +00:00
Michael Weiss
17c4f6fa36
chromium: Make get-commit-message.py more robust
...
Not all updates contain security fixes.
2021-03-07 12:05:21 +01:00
Michael Weiss
095ad1b5b9
Merge pull request #115243 from primeos/chromium
...
chromium: 89.0.4389.72 -> 89.0.4389.82
2021-03-07 11:38:22 +01:00
github-actions[bot]
65cddb74d7
Merge staging-next into staging
2021-03-07 06:17:25 +00:00
Sandro
d2f184c8b0
Merge pull request #115271 from yoctocell/tor-browser-bundle
...
tor-browser-bundle-bin: 10.0.12 -> 10.0.13
2021-03-07 04:03:29 +01:00
github-actions[bot]
f9d4095295
Merge staging-next into staging
2021-03-07 00:41:13 +00:00
Xinglu Chen
39b57a4d0d
tor-browser-bundle-bin: 10.0.12 -> 10.0.13
...
Update to latest release.
<https://blog.torproject.org/new-release-tor-browser-10013 >
2021-03-06 21:31:52 +01:00
John Ericson
f5a7d8bb41
Merge pull request #115228 from siraben/unzip-buildInputs
...
treewide: unzip buildInputs to nativeBuildInputs (2)
2021-03-06 13:30:43 -05:00
Michael Weiss
b1c5aa5ef1
chromium: 89.0.4389.72 -> 89.0.4389.82
2021-03-06 11:59:38 +01:00
Ben Siraphob
4f0cdb68d7
treewide: unzip buldInputs to nativeBuildInputs (2)
2021-03-06 15:18:05 +07:00
Anton Kindestam
18b479e782
nyxt: change meta.platforms to platforms.all
...
This builds and works fine on at least aarch64 (tested on a PineBook
Pro), so I figure the arbitrary platform limitation ought to be
lifted.
2021-03-06 07:15:32 +01:00
github-actions[bot]
4af94cf9a3
Merge staging-next into staging
2021-03-05 12:20:56 +00:00
Michael Weiss
6abbdecf62
Merge pull request #114977 from primeos/chromium-remove-client-credentials
...
chromium: Remove google_default_client_{id,secret}
2021-03-05 13:08:09 +01:00
Jan Tojnar
6d1958ad2d
Merge branch 'staging-next' into staging
2021-03-04 22:16:45 +01:00
Michael Weiss
8671fe7c90
chromiumDev: 90.0.4427.5 -> 90.0.4430.11
2021-03-04 11:50:46 +01:00
Sean Buckley
fcd759da4e
brave: 1.20.110 -> 1.21.73
2021-03-03 19:26:15 -05:00
Sandro
ac1c20756c
Merge pull request #114717 from AndersonTorres/new-luakit
...
luakit: 2.2.1 -> 2.3
2021-03-04 01:05:06 +01:00
Michael Weiss
9004162c26
chromium: Add my script to generate the commit messages
...
Might not be that readable and reliable but it should get the job done.
2021-03-03 16:55:03 +01:00
Michael Weiss
dc9f2c5e70
chromium: Remove google_default_client_{id,secret}
...
Reason: Google is limiting access to their private Chrome APIs starting
on March 15, 2021 [0]. Closes #110245 .
From the mailing list thread [1]:
"The changes we announced affect the OAuth 2.0 client id and secret
which are used for signing into Chrome, not the API key."
"To avoid using that API, it's sufficient to either not set the OAuth
2.0 credentials, or disabling the Google signin integration" (e.g. by
passing the flag --allow-browser-signin=false)
[0]: https://blog.chromium.org/2021/01/limiting-private-api-availability-in.html
[1]: https://groups.google.com/a/chromium.org/g/chromium-packagers/c/SG6jnsP4pWM/
2021-03-03 13:13:17 +01:00
Michael Weiss
9f38162b30
chromium: 88.0.4324.182 -> 89.0.4389.72
...
https://chromereleases.googleblog.com/2021/03/stable-channel-update-for-desktop.html
This update includes 47 security fixes. Google is aware of reports that
an exploit for CVE-2021-21166 exists in the wild.
CVEs:
CVE-2021-21159 CVE-2021-21160 CVE-2021-21161 CVE-2021-21162
CVE-2021-21163 CVE-2021-21164 CVE-2021-21165 CVE-2021-21166
CVE-2021-21167 CVE-2021-21168 CVE-2021-21169 CVE-2021-21170
CVE-2021-21171 CVE-2021-21172 CVE-2021-21173 CVE-2021-21174
CVE-2021-21175 CVE-2021-21176 CVE-2021-21177 CVE-2021-21178
CVE-2021-21179 CVE-2021-21180 CVE-2020-27844 CVE-2021-21181
CVE-2021-21182 CVE-2021-21183 CVE-2021-21184 CVE-2021-21185
CVE-2021-21186 CVE-2021-21187 CVE-2021-21188 CVE-2021-21189
CVE-2021-21190
2021-03-03 12:23:11 +01:00
github-actions[bot]
eef2c4e401
Merge staging-next into staging
2021-03-03 00:38:15 +00:00
Michael Weiss
f4c885a79a
chromiumBeta: 89.0.4389.69 -> 89.0.4389.72
2021-03-02 20:28:11 +01:00
Jan Tojnar
913394a1d9
Merge branch 'staging-next' into staging
2021-03-01 19:30:56 +01:00
AndersonTorres
70ef3914bc
luakit: 2.2.1 -> 2.3
2021-03-01 15:03:41 -03:00
Pavol Rusnak
932764af1f
Merge pull request #114209 from nicbk/master
...
tor-browser-bundle-bin: 10.0.9 -> 10.0.12
2021-02-28 22:12:55 +01:00
github-actions[bot]
5267db2989
Merge staging-next into staging
2021-02-27 18:16:44 +00:00
Michael Weiss
5240639ab6
chromiumDev: 90.0.4421.5 -> 90.0.4427.5
2021-02-27 16:35:48 +01:00
Michael Weiss
adccc8b65b
chromiumBeta: 89.0.4389.58 -> 89.0.4389.69
2021-02-27 16:35:48 +01:00
github-actions[bot]
2a38839b78
Merge staging-next into staging
2021-02-27 12:20:00 +00:00
zimbatm
bdfd50116a
Revert "mdsh: 0.5.0 -> 0.6.0"
...
This was pushed by mistake!
This reverts commit 7ee7b5deec
2021-02-26 22:54:37 +01:00
zimbatm
7ee7b5deec
mdsh: 0.5.0 -> 0.6.0
2021-02-26 22:52:59 +01:00
adisbladis
92f2c8b4ac
firefox-bin: Remove alsa/libpulseaudio dev outputs
...
It doesn't seem that these make any functional difference, but they are
increasing the closure size.
2021-02-26 19:07:52 +02:00
Robert Schütz
54757b35c1
Merge branch 'staging-next' into staging
2021-02-26 10:56:17 +01:00
Frederik Rietdijk
c456a2512f
Merge master into staging-next
2021-02-26 10:25:13 +01:00
Mario Rodas
c39abeec9d
Merge pull request #114313 from buckley310/brave
...
brave: 1.19.88 -> 1.20.110
2021-02-25 08:54:44 -05:00
Sean Buckley
504a933df7
brave: 1.19.88 -> 1.20.110
2021-02-24 23:07:11 -05:00
Bernardo Meurer
f6b5bfdb47
Merge pull request #114236 from taku0/firefox-bin-86.0
...
firefox-bin: 85.0.2 -> 86.0 [High security fixes]
2021-02-24 18:30:23 +00:00
Martin Weinelt
7b9c874d67
firefox-esr: 78.7.1esr -> 78.8.0esr
...
/cc original PR #114152 . ESR doesn't need to go through staging.
I briefly ran it on X11 x86_64 NixOS and checked build on aarch64.
(for other's testing see the PR linked above)
2021-02-24 18:41:30 +01:00
Martin Weinelt
059e818b2f
firefox: 85.0.2 -> 86.0
2021-02-24 15:06:49 +01:00
Martin Weinelt
841fcbdb17
firefox-esr: 78.7.1esr -> 78.8.0esr
2021-02-24 15:06:49 +01:00
