-
-
Notifications
You must be signed in to change notification settings - Fork 14.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
electron_30-bin: mark as insecure because it's EOL, electron-source.electron_30: remove as it's EOL #350549
Conversation
Electron versions sure do get deprecated fast... I'll take a look at Webcord soon. |
@NovusTheory is ytmdesktop in a position to cut a release with its latest changes (notably, electron 33)? |
I'll take a look at teams-for-linux, real quick. Have an open PR #350497 already so I'll bump it in there. |
@cjshearer I was mostly working on and waiting on some feature branches to be ready and merging everything in for a 2.1 release but I can look over getting a patch release of 2.0.6 pushed which can at least upgrade electron to 33 at minimum in the stable builds. Our dev branch already has the app updated to electron 33 so we should be ready in that sense. |
webcord-vencord bump in #350622. Really unfortunate that we must lag behind latest electron, but it is what it is. |
If nobody objects, I can tackle the antares package as well - got some free time in my hands. Edit: I did it anyway. |
bilibili can't work properly on newer electron. We should use electron from upstream or use electron_30-bin. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for taking care of this 🙌
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks! :)
This was supposed to be merged one day before restricting all breaking changes, but there was a typo in the announcement they changed yesterday. At any rate, this does place us right in the "restrict all breaking changes" phase since a few hours. @RossComputerGuy feel free to merge this PR now, a few hours late, or over the span of the next few days. |
Security trumps the freeze, I think this is fine. |
ytmdesktop PR for updating ytmdesktop from 2.0.5 -> 2.0.6, which bumps electron from 30 -> 33. Thanks for the quick turnaround @NovusTheory! |
Result of 4 packages marked as broken and skipped:
4 packages built:
|
Will merge this on Wednesday. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks!
EDIT: Oh, I already approved 😆
Backport failed for Please cherry-pick the changes locally and resolve any conflicts. git fetch origin release-24.05
git worktree add -d .worktree/backport-350549-to-release-24.05 origin/release-24.05
cd .worktree/backport-350549-to-release-24.05
git switch --create backport-350549-to-release-24.05
git cherry-pick -x 14e79e787e654b34df599aee6d721d6f873f4358 87b49e959537f9891d3c258324f750ead9878f7f |
I intend to merge this a week from now,
2024-10-30
, a day before ZHF (see #339153)A week or so too late but here we go:
This marks the binary variant of
electron_30
as insecure and removes the source build.electron_30
reached its end of life on2024-10-15
, see https://www.electronjs.org/docs/latest/tutorial/electron-timelines#timeline.You may also want to see #335850 from a few weeks ago doing the same thing for
electron_29
.It provides some context for how this usually works.
At any rate, the following packages are affected by this and need to move to some newer not-yet-EOL
electron
release:Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)nixpkgs-review
resultGenerated using
nixpkgs-review
.Command:
nixpkgs-review pr 350549
x86_64-linux