Skip to content

Comments

electron_34-bin: mark as insecure because it's EOL; electron-source.electron_34: remove as it's EOL#419903

Merged
TomaSajt merged 2 commits intoNixOS:masterfrom
TomaSajt:electron34-eol
Jun 30, 2025
Merged

electron_34-bin: mark as insecure because it's EOL; electron-source.electron_34: remove as it's EOL#419903
TomaSajt merged 2 commits intoNixOS:masterfrom
TomaSajt:electron34-eol

Conversation

@TomaSajt
Copy link
Contributor

@TomaSajt TomaSajt commented Jun 25, 2025

Previously:

electron_34 will be EOL soon (2025-06-24).
https://www.electronjs.org/docs/latest/tutorial/electron-timelines (permalink)

This PR removes the source build on Linux for electron 34 and marks the binary variants for Darwin and Linux as insecure.
electron_34 will still be available for an undetermined while. Linux will simply use the binary package instead of the source build, just like Darwin.

After this PR has been merged, users will be able opt-into the EOL version of electron as outlined by this eval error message:

error: Package ‘electron-34.5.8’ in /path/to/nixpkgs/pkgs/development/tools/electron/binary/generic.nix:43 is marked as insecure, refusing to evaluate.


Known issues:
- Electron version 34.5.8 is EOL

You can install it anyway by allowing this package, using the
following methods:

a) To temporarily allow all insecure packages, you can use an environment
  variable for a single invocation of the nix tools:

    $ export NIXPKGS_ALLOW_INSECURE=1

  Note: When using `nix shell`, `nix build`, `nix develop`, etc with a flake,
        then pass `--impure` in order to allow use of environment variables.

b) for `nixos-rebuild` you can add ‘electron-34.5.8’ to
  `nixpkgs.config.permittedInsecurePackages` in the configuration.nix,
  like so:

    {
      nixpkgs.config.permittedInsecurePackages = [
        "electron-34.5.8"
      ];
    }

c) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  ‘electron-34.5.8’ to `permittedInsecurePackages` in
  ~/.config/nixpkgs/config.nix, like so:

    {
      permittedInsecurePackages = [
        "electron-34.5.8"
      ];
    }

The following packages are affected by this. Note that those package will continue to work, but users will be presented with the eval error above and have to opt-in.

If you are pinged as one of the maintainers of such package, you can do one of the following:

  1. Check if upstream supports a newer electron version and open a PR in nixpkgs to use that instead OR
  2. Try using a newer electron version than upstream suggests and if that turns out to be stable, open a PR in nixpkgs to use that instead OR
  3. Do nothing in nixpkgs, and maybe make upstream aware that their electron version is EOL.

Things done

  • Built on platform(s)
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin
  • For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
    • sandbox = relaxed
    • sandbox = true
  • Tested, as applicable:
  • Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
  • Tested basic functionality of all binary files (usually in ./result/bin/)
  • Nixpkgs 25.11 Release Notes (or backporting 24.11 and 25.05 Nixpkgs Release notes)
    • (Package updates) Added a release notes entry if the change is major or breaking
  • NixOS 25.11 Release Notes (or backporting 24.11 and 25.05 NixOS Release notes)
    • (Module updates) Added a release notes entry if the change is significant
    • (Module addition) Added a release notes entry if adding a new NixOS module
  • Fits CONTRIBUTING.md, pkgs/README.md, maintainers/README.md and other contributing documentation in corresponding paths.

Add a 👍 reaction to pull requests you find important.

@nixpkgs-ci nixpkgs-ci bot added 10.rebuild-linux: 11-100 This PR causes between 11 and 100 packages to rebuild on Linux. 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin. labels Jun 25, 2025
@TomaSajt TomaSajt mentioned this pull request Jun 25, 2025
13 tasks
@amarshall
Copy link
Member

Re bitwarden-desktop: the next release will use Electron 36; we could backport it (from bitwarden/clients#14725) in the meantime. However, I likely won’t be able to do that for another day or two, if someone wants to build and test in the meantime, feel free.

@SuperSandro2000
Copy link
Member

They want to do a new release tomorrow actually bitwarden/clients#14725 (comment) so we can just wait for that.

@teutat3s teutat3s added 11.by: package-maintainer This PR was created by a maintainer of all the package it changes. 12.approvals: 1 This PR was reviewed and approved by one person. 12.approved-by: package-maintainer This PR was reviewed and approved by a maintainer listed in any of the changed packages. labels Jun 26, 2025
@nixpkgs-ci nixpkgs-ci bot removed 11.by: package-maintainer This PR was created by a maintainer of all the package it changes. 12.approved-by: package-maintainer This PR was reviewed and approved by a maintainer listed in any of the changed packages. labels Jun 26, 2025
@NotAShelf
Copy link
Member

I'll update webcord-vencord tomorrow (roughly 16 hours from now on.)

@SuperSandro2000

This comment was marked as outdated.

@NotAShelf
Copy link
Member

I've opened 420519 for webcord-vencord. Further testing would be appreciated.

@teutat3s
Copy link
Member

Now that #420250 is merged, let's merge this too. We want a maximum of 3 versions of electron built from source.

@TomaSajt
Copy link
Contributor Author

Alright.

So, since we're backporting this, ideally, all the PRs above for the dependent packages should also get backported, right?

@TomaSajt TomaSajt merged commit 02876cf into NixOS:master Jun 30, 2025
66 of 67 checks passed
@nixpkgs-ci
Copy link
Contributor

nixpkgs-ci bot commented Jun 30, 2025

@NotAShelf
Copy link
Member

Could someone also merge #420519 before users start getting warnings about electron?

@liff liff mentioned this pull request Jul 2, 2025
13 tasks
@teutat3s
Copy link
Member

teutat3s commented Jul 3, 2025

For the record, deltachat-desktop did bump their electron version recently, but there hasn't been a new release yet. deltachat/deltachat-desktop@3096a70

@dotlambda
Copy link
Member

For the record, deltachat-desktop did bump their electron version recently, but there hasn't been a new release yet. deltachat/deltachat-desktop@3096a70

And I'm having trouble building the newest version. It can't find esbuild for some reason.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

1.severity: security Issues which raise a security issue, or PRs that fix one 8.has: port to stable This PR already has a backport to the stable release. 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin. 10.rebuild-linux: 11-100 This PR causes between 11 and 100 packages to rebuild on Linux. 12.approvals: 1 This PR was reviewed and approved by one person.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants