[3.23] backports/electron: upgrade to 39.3.0 #1967

Open
forge wants to merge 1 commit from electron/upgrade-39.3.0 into v3.23
Owner
No description provided.
backports/electron: upgrade to 39.3.0
Some checks failed
/ build-armv7 (pull_request) Successful in 54s
/ deploy-armv7 (pull_request) Successful in 33s
/ build-x86_64 (pull_request) Failing after 6m1s
/ deploy-x86_64 (pull_request) Has been skipped
/ lint (pull_request) Successful in 26s
/ build-aarch64 (pull_request) Successful in 1h48m21s
/ deploy-aarch64 (pull_request) Successful in 40s
10f7726eb2
Some checks failed
/ build-armv7 (pull_request) Successful in 54s
/ deploy-armv7 (pull_request) Successful in 33s
/ build-x86_64 (pull_request) Failing after 6m1s
/ deploy-x86_64 (pull_request) Has been skipped
/ lint (pull_request) Successful in 26s
/ build-aarch64 (pull_request) Successful in 1h48m21s
/ deploy-aarch64 (pull_request) Successful in 40s
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin electron/upgrade-39.3.0:electron/upgrade-39.3.0
git switch electron/upgrade-39.3.0

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch v3.23
git merge --no-ff electron/upgrade-39.3.0
git switch electron/upgrade-39.3.0
git rebase v3.23
git switch v3.23
git merge --ff-only electron/upgrade-39.3.0
git switch electron/upgrade-39.3.0
git rebase v3.23
git switch v3.23
git merge --no-ff electron/upgrade-39.3.0
git switch v3.23
git merge --squash electron/upgrade-39.3.0
git switch v3.23
git merge --ff-only electron/upgrade-39.3.0
git switch v3.23
git merge electron/upgrade-39.3.0
git push origin v3.23
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
forge/ayaports!1967
No description provided.