nordic-dev.net/nixpkgs
nordic-dev.net/nixpkgs
2
0
Fork 0
mirror of https://github.com/NixOS/nixpkgs.git synced 2024-12-29 00:53:57 +00:00
Code Issues Packages Projects Releases Wiki Activity
2dbc8f62d8
nixpkgs/pkgs/applications/networking/browsers/chromium/upstream-info.nix

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

40 lines
1.3 KiB
Nix
Raw Normal View History

chromium,ungoogled-chromium: fix ofborg maintainer pings ofborg uses `builtins.unsafeGetAttrPos` internally, to figure out which maintainers need to be pinged. e.g: `builtins.unsafeGetAttrPos "version" drv` When using a `.json` file containing the version via `lib.importJSON`, this will always return `null` and thus leading to no pings at all. This commit works around this, resulting in properly working pings for any changes to the upstream-info file. A similar thing has been done for element-{web,desktop} in the past.
2023-07-29 16:53:34 +00:00
{
stable = {
chromedriver = {
chromedriver: 122.0.6261.69 -> 122.0.6261.94
2024-02-27 22:28:41 +00:00
hash_darwin = "sha256-iv370BYH8HobUxeYbsV4/A6JyZG2feEuVbJCLVZc3Og=";
chromium,chromedriver,electron: use hash instead of sha256 everywhere this patch updates the packaging of chromium and chromedriver to use sri hashes in `upstream-info.nix` instead of sha256 as well as the packaging of electron to use sri hashes in `info.json` instead of sha256 (just gn). this patch also updates the previous `sha256` values in `upstream-info.nix` and `info.json` to sri hashes in `hash`.
2023-10-21 11:02:47 +00:00
hash_darwin_aarch64 =
chromedriver: 122.0.6261.69 -> 122.0.6261.94
2024-02-27 22:28:41 +00:00
"sha256-Gc0OXG7dx5Mvy0aAsnqVIJtPFK8OYmFr8Ofy+UXacM4=";
hash_linux = "sha256-ZcN/v7co08aRWM88s93nBU/FLEfE7JGf/hEH0tk3qy8=";
version = "122.0.6261.94";
chromium,ungoogled-chromium: fix ofborg maintainer pings ofborg uses `builtins.unsafeGetAttrPos` internally, to figure out which maintainers need to be pinged. e.g: `builtins.unsafeGetAttrPos "version" drv` When using a `.json` file containing the version via `lib.importJSON`, this will always return `null` and thus leading to no pings at all. This commit works around this, resulting in properly working pings for any changes to the upstream-info file. A similar thing has been done for element-{web,desktop} in the past.
2023-07-29 16:53:34 +00:00
};
deps = {
gn = {
chromium: 121.0.6167.184 -> 122.0.6261.57 https://chromereleases.googleblog.com/2024/02/stable-channel-update-for-desktop_20.html This update includes 12 security fixes. CVEs: CVE-2024-1669 CVE-2024-1670 CVE-2024-1671 CVE-2024-1672 CVE-2024-1673 CVE-2024-1674 CVE-2024-1675 CVE-2024-1676
2024-02-21 00:58:20 +00:00
hash = "sha256-UhdDsq9JyP0efGpAaJ/nLp723BbjM6pkFPcAnQbgMKY=";
rev = "f99e015ac35f689cfdbf46e4eb174e5d2da78d8e";
chromium,ungoogled-chromium: fix ofborg maintainer pings ofborg uses `builtins.unsafeGetAttrPos` internally, to figure out which maintainers need to be pinged. e.g: `builtins.unsafeGetAttrPos "version" drv` When using a `.json` file containing the version via `lib.importJSON`, this will always return `null` and thus leading to no pings at all. This commit works around this, resulting in properly working pings for any changes to the upstream-info file. A similar thing has been done for element-{web,desktop} in the past.
2023-07-29 16:53:34 +00:00
url = "https://gn.googlesource.com/gn";
chromium: 121.0.6167.184 -> 122.0.6261.57 https://chromereleases.googleblog.com/2024/02/stable-channel-update-for-desktop_20.html This update includes 12 security fixes. CVEs: CVE-2024-1669 CVE-2024-1670 CVE-2024-1671 CVE-2024-1672 CVE-2024-1673 CVE-2024-1674 CVE-2024-1675 CVE-2024-1676
2024-02-21 00:58:20 +00:00
version = "2024-01-22";
chromium,ungoogled-chromium: fix ofborg maintainer pings ofborg uses `builtins.unsafeGetAttrPos` internally, to figure out which maintainers need to be pinged. e.g: `builtins.unsafeGetAttrPos "version" drv` When using a `.json` file containing the version via `lib.importJSON`, this will always return `null` and thus leading to no pings at all. This commit works around this, resulting in properly working pings for any changes to the upstream-info file. A similar thing has been done for element-{web,desktop} in the past.
2023-07-29 16:53:34 +00:00
};
};
chromium: 122.0.6261.94 -> 122.0.6261.111 https://chromereleases.googleblog.com/2024/03/stable-channel-update-for-desktop.html This update includes 3 security fixes. CVEs: CVE-2024-2173 CVE-2024-2174 CVE-2024-2176
2024-03-06 20:55:33 +00:00
hash = "sha256-43h11bx/k78W7fEPZz4LwxNVExwGSSt74mlbiUYf5ig=";
hash_deb_amd64 = "sha256-juwTFdJB1hgAA14aabNIrql5aaP1JWQy7nOsoTF2Vto=";
version = "122.0.6261.111";
chromium,ungoogled-chromium: fix ofborg maintainer pings ofborg uses `builtins.unsafeGetAttrPos` internally, to figure out which maintainers need to be pinged. e.g: `builtins.unsafeGetAttrPos "version" drv` When using a `.json` file containing the version via `lib.importJSON`, this will always return `null` and thus leading to no pings at all. This commit works around this, resulting in properly working pings for any changes to the upstream-info file. A similar thing has been done for element-{web,desktop} in the past.
2023-07-29 16:53:34 +00:00
};
ungoogled-chromium = {
deps = {
gn = {
ungoogled-chromium: 121.0.6167.184-1 -> 122.0.6261.69-1 https://chromereleases.googleblog.com/2024/02/stable-channel-update-for-desktop_22.html https://chromereleases.googleblog.com/2024/02/stable-channel-update-for-desktop_20.html This update includes 12 security fixes. CVEs: CVE-2024-1669 CVE-2024-1670 CVE-2024-1671 CVE-2024-1672 CVE-2024-1673 CVE-2024-1674 CVE-2024-1675 CVE-2024-1676
2024-02-23 21:06:28 +00:00
hash = "sha256-UhdDsq9JyP0efGpAaJ/nLp723BbjM6pkFPcAnQbgMKY=";
rev = "f99e015ac35f689cfdbf46e4eb174e5d2da78d8e";
chromium,ungoogled-chromium: fix ofborg maintainer pings ofborg uses `builtins.unsafeGetAttrPos` internally, to figure out which maintainers need to be pinged. e.g: `builtins.unsafeGetAttrPos "version" drv` When using a `.json` file containing the version via `lib.importJSON`, this will always return `null` and thus leading to no pings at all. This commit works around this, resulting in properly working pings for any changes to the upstream-info file. A similar thing has been done for element-{web,desktop} in the past.
2023-07-29 16:53:34 +00:00
url = "https://gn.googlesource.com/gn";
ungoogled-chromium: 121.0.6167.184-1 -> 122.0.6261.69-1 https://chromereleases.googleblog.com/2024/02/stable-channel-update-for-desktop_22.html https://chromereleases.googleblog.com/2024/02/stable-channel-update-for-desktop_20.html This update includes 12 security fixes. CVEs: CVE-2024-1669 CVE-2024-1670 CVE-2024-1671 CVE-2024-1672 CVE-2024-1673 CVE-2024-1674 CVE-2024-1675 CVE-2024-1676
2024-02-23 21:06:28 +00:00
version = "2024-01-22";
chromium,ungoogled-chromium: fix ofborg maintainer pings ofborg uses `builtins.unsafeGetAttrPos` internally, to figure out which maintainers need to be pinged. e.g: `builtins.unsafeGetAttrPos "version" drv` When using a `.json` file containing the version via `lib.importJSON`, this will always return `null` and thus leading to no pings at all. This commit works around this, resulting in properly working pings for any changes to the upstream-info file. A similar thing has been done for element-{web,desktop} in the past.
2023-07-29 16:53:34 +00:00
};
ungoogled-patches = {
ungoogled-chromium: 122.0.6261.94-1 -> 122.0.6261.111-1 https://chromereleases.googleblog.com/2024/03/stable-channel-update-for-desktop.html This update includes 3 security fixes. CVEs: CVE-2024-2173 CVE-2024-2174 CVE-2024-2176
2024-03-07 01:40:35 +00:00
hash = "sha256-7c4VQLotLHmSFKfzzXrlwXKB3XPFpyRTnuATrS9RfEw=";
rev = "122.0.6261.111-1";
chromium,ungoogled-chromium: fix ofborg maintainer pings ofborg uses `builtins.unsafeGetAttrPos` internally, to figure out which maintainers need to be pinged. e.g: `builtins.unsafeGetAttrPos "version" drv` When using a `.json` file containing the version via `lib.importJSON`, this will always return `null` and thus leading to no pings at all. This commit works around this, resulting in properly working pings for any changes to the upstream-info file. A similar thing has been done for element-{web,desktop} in the past.
2023-07-29 16:53:34 +00:00
};
};
ungoogled-chromium: 122.0.6261.94-1 -> 122.0.6261.111-1 https://chromereleases.googleblog.com/2024/03/stable-channel-update-for-desktop.html This update includes 3 security fixes. CVEs: CVE-2024-2173 CVE-2024-2174 CVE-2024-2176
2024-03-07 01:40:35 +00:00
hash = "sha256-43h11bx/k78W7fEPZz4LwxNVExwGSSt74mlbiUYf5ig=";
hash_deb_amd64 = "sha256-juwTFdJB1hgAA14aabNIrql5aaP1JWQy7nOsoTF2Vto=";
version = "122.0.6261.111";
chromium,ungoogled-chromium: fix ofborg maintainer pings ofborg uses `builtins.unsafeGetAttrPos` internally, to figure out which maintainers need to be pinged. e.g: `builtins.unsafeGetAttrPos "version" drv` When using a `.json` file containing the version via `lib.importJSON`, this will always return `null` and thus leading to no pings at all. This commit works around this, resulting in properly working pings for any changes to the upstream-info file. A similar thing has been done for element-{web,desktop} in the past.
2023-07-29 16:53:34 +00:00
};
}
Reference in New Issue Copy Permalink