src: throw RangeError on failed ArrayBuffer BackingStore allocation

https://github.com/nodejs/node/pull/61480

.claude/skills/electron-chromium-upgrade/SKILL.md

@@ -7,14 +7,13 @@ description: Guide for performing Chromium version upgrades in the Electron proj
 
 ## Summary
 
-Run `e sync --3` repeatedly, fixing patch conflicts as they arise, until it succeeds. Then run `e patches all` and commit changes atomically.
+Run `e sync --3` repeatedly, fixing patch conflicts as they arise, until it succeeds. Then export patches and commit changes atomically.
 
 ## Success Criteria
 
 Phase One is complete when:
 - `e sync --3` exits with code 0 (no patch failures)
-- `e patches all` has been run to export all changes
-- All changes are committed per the commit guidelines below
+- All changes are committed per the commit guidelines
 
 Do not stop until these criteria are met.
 
@@ -30,12 +29,18 @@ The `roller/chromium/main` branch is created by automation to update Electron's
 - `patches/`: Patch files organized by target
 - `docs/development/patches.md`: Patch system documentation
 
+## Pre-flight Checks
+
+Run these once at the start of each upgrade session:
+
+1. **Clear rerere cache** (if enabled): `git rerere clear` in both the electron and `..` repos. Stale recorded resolutions from a prior attempt can silently apply wrong merges.
+2. **Ensure pre-commit hooks are installed**: Check that `.git/hooks/pre-commit` exists. If not, run `yarn husky` to install it. The hook runs `lint-staged` which handles clang-format for C++ files.
+
 ## Workflow
 
-1. Delete the `.git/rr-cache` in both the `electron` and `..` folder to ensure no accidental rerere replays occur from before this upgrade phase attempt started
-2. Run `e sync --3` (the `--3` flag enables 3-way merge, always required)
-3. If succeeds → skip to step 6
-4. If patch fails:
+1. Run `e sync --3` (the `--3` flag enables 3-way merge, always required)
+2. If succeeds → skip to step 5
+3. If patch fails:
    - Identify target repo and patch from error output
    - Analyze failure (see references/patch-analysis.md)
    - Fix conflict in target repo's working directory
@@ -43,10 +48,8 @@ The `roller/chromium/main` branch is created by automation to update Electron's
    - Repeat until all patches for that repo apply
    - IMPORTANT: Once `git am --continue` succeeds you MUST run `e patches {target}` to export fixes
    - Return to step 1
-5. When `e sync --3` succeeds, run `e patches all`
-6. **Read `references/phase-one-commit-guidelines.md` NOW**, then commit changes following those instructions exactly.
-
-Before committing any Phase One changes, you MUST read `references/phase-one-commit-guidelines.md` and follow its instructions exactly.
+4. When `e sync --3` succeeds, run `e patches all`
+5. **Read `references/phase-one-commit-guidelines.md` NOW**, then commit changes following those instructions exactly.
 
 ## Commands Reference
 
@@ -56,6 +59,7 @@ Before committing any Phase One changes, you MUST read `references/phase-one-com
 | `git am --continue` | Continue after resolving conflict (run in target repo) |
 | `e patches {target}` | Export commits from target repo to patch files |
 | `e patches all` | Export all patches from all targets |
+| `e patches {target} --commit-updates` | Export patches and auto-commit trivial changes |
 | `e patches --list-targets` | List targets and config paths |
 
 ## Patch System Mental Model
@@ -81,24 +85,20 @@ Fix existing patches 99% of the time rather than creating new ones.
 2. **Never change TODO assignees**: `TODO(name)` must retain original name
 3. **Update descriptions**: If upstream changed (e.g., `DCHECK` → `CHECK_IS_TEST`), update patch commit message to reflect current state
 
-## Final Deliverable
-
-After Phase One, write a summary of every change: what was fixed, why, reasoning, and Chromium CL links.
-
 # Electron Chromium Upgrade: Phase Two
 
 ## Summary
 
-Run `e build -k 999` repeatedly, fixing build issues as they arise, until it succeeds. Then run `e start --version` to validate Electron launches and commit changes atomically.
+Run `e build -k 999 -- --quiet` repeatedly, fixing build issues as they arise, until it succeeds. Then run `e start --version` to validate Electron launches and commit changes atomically.
 
 Run Phase Two immediately after Phase One is complete.
 
 ## Success Criteria
 
 Phase Two is complete when:
-- `e build -k 999` exits with code 0 (no build failures)
+- `e build -k 999 -- --quiet` exits with code 0 (no build failures)
 - `e start --version` has been run to check Electron launches
-- All changes are committed per the commit guidelines below
+- All changes are committed per the commit guidelines
 
 Do not stop until these criteria are met. Do not delete code or features, never comment out code in order to take short cut. Make all existing code, logic and intention work.
 
@@ -112,8 +112,7 @@ The `roller/chromium/main` branch is created by automation to update Electron's
 
 ## Workflow
 
-1. Run `e build -k 999` (the `-k 999` flag is a flag to ninja to say "do not stop until you find that many errors" it is an attempt to get as much error
-  context as possible for each time we run build)
+1. Run `e build -k 999 -- --quiet` (the `--quiet` flag suppresses per-target status lines, showing only errors and the final result)
 2. If succeeds → skip to step 6
 3. If build fails:
     - Identify underlying file in "electron" from the compilation error message
@@ -126,27 +125,17 @@ The `roller/chromium/main` branch is created by automation to update Electron's
 4. **CRITICAL**: After ANY commit (especially patch commits), immediately run `git status` in the electron repo
     - Look for other modified `.patch` files that only have index/hunk header changes
     - These are dependent patches affected by your fix
-    - Commit them immediately with: `git commit -am "chore: update patch hunk headers"`
-    - This prevents losing track of necessary updates
+    - Commit them immediately with: `git commit -am "chore: update patches (trivial only)"`
 5. Return to step 1
 6. When `e build` succeeds, run `e start --version`
 7. Check if you have any pending changes in the Chromium repo by running `git status`
     - If you have changes follow the instructions below in "A. Patch Fixes" to correctly commit those modifications into the appropriate patch file
 
-Before committing any Phase Two changes, you MUST read `references/phase-two-commit-guidelines.md` and follow its instructions exactly.
-
-## Build Error Detection
-
-When monitoring `e build -k 999` output, filter for errors using this regex pattern:
-error:|FAILED:|fatal:|subcommand failed|build finished
-
-The build output is extremely verbose. Filtering is essential to catch errors quickly.
-
 ## Commands Reference
 
 | Command | Purpose |
 |---------|---------|
-| `e build -k 999` | Builds Electron and won't stop until either all targets attempted or 999 errors found |
+| `e build -k 999 -- --quiet` | Build Electron, continue on errors, suppress status lines |
 | `e build -t {target}.o` | Build just one specific target to verify a fix |
 | `e start --version` | Validate Electron launches after successful build |
 
@@ -163,28 +152,21 @@ When the error is in a file that Electron patches (check with `grep -l "filename
     git add <modified-file>
     git commit --fixup=<original-patch-commit-hash>
     GIT_SEQUENCE_EDITOR=: git rebase --autosquash --autostash -i <commit>^
-3. Export the updated patch: e patches chromium
-4. Commit the updated patch file in the electron repo following the `references/phase-one-commit-guidelines.md`, then commit changes following those instructions exactly. **READ THESE GUIDELINES BEFORE COMMITTING THESE CHANGES**
+    ```
+3. Export the updated patch: `e patches chromium`
+4. Commit the updated patch file following `references/phase-one-commit-guidelines.md`.
 
 To find the original patch commit to fixup: `git log --oneline | grep -i "keyword from patch name"`
 
 The base commit for rebase is the Chromium commit before patches were applied. Find it by checking the `refs/patches/upstream-head` ref.
 
-B. Electron Code Fixes (for files in shell/, electron/, etc.)
+### B. Electron Code Fixes (for files in shell/, electron/, etc.)
 
 When the error is in Electron's own source code:
 
 1. Edit files directly in the electron repo
 2. Commit directly (no patch export needed)
 
-Dependent Patch Updates
-
-IMPORTANT: When you modify a patch, other patches that apply to the same file may have their hunk headers invalidated. After committing a patch fix:
-
-1. Run git status in the electron repo
-2. Look for other modified .patch files with just index/hunk header changes
-3. Commit these with: git commit -m "chore: update patch hunk headers"
-
 # Critical: Read Before Committing
 
 - Before ANY Phase One commits: Read `references/phase-one-commit-guidelines.md`
@@ -196,4 +178,4 @@ This skill has additional reference files in `references/`:
 - phase-one-commit-guidelines.md - Commit format for Phase One
 - phase-two-commit-guidelines.md - Commit format for Phase Two
 
-Read these when referenced in the workflow steps.
+Read these when referenced in the workflow steps.

.claude/skills/electron-chromium-upgrade/references/patch-analysis.md

@@ -17,6 +17,56 @@
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/{CL_NUMBER}
    ```
 
+## Critical: Resolve by Intent, Not by Mechanical Merge
+
+When resolving a patch conflict, do NOT blindly preserve the patch's old code. Instead:
+
+1. **Understand the upstream CL's full scope** — not just the conflicting hunk.
+   Run `git show <commit> --stat` and read diffs for all affected files.
+   Upstream may have removed structs, members, or methods that the patch
+   references in other hunks or files.
+
+2. **Re-read the patch commit message** to understand its *intent* — what
+   behavior does it need to preserve or add?
+
+3. **Implement the intent against the new upstream code.** If the patch's
+   purpose is "add a feature flag guard", add only the guard — don't also
+   restore old code inside the guard that upstream separately removed.
+
+### Lesson: Upstream Removals Break Patch References
+
+- **Trigger:** Patch conflict involves an upstream refactor (not just context drift)
+- **Strategy:** After identifying the upstream CL, check its full diff for
+  removed types, members, and methods. If the patch's old code references
+  something removed, the resolution must use the new upstream mechanism.
+- **Evidence:** An upstream CL removed a `HeadlessModeWindow` struct from a
+  header, but the conflict was only in a `.mm` file. Mechanically keeping the
+  patch's old line (`headless_mode_window_ = ...`) produced code referencing
+  a nonexistent type — caught only on review, not at patch-apply time.
+
+### Lesson: Separate Patch Purpose from Patch Implementation
+
+- **Trigger:** Conflict between "upstream simplified code" vs "patch has older code"
+- **Strategy:** Identify the *minimal* change the patch needs. If the patch
+  wraps code in a conditional, only add the conditional — don't restore old
+  code that was inside the conditional but was separately cleaned up upstream.
+- **Evidence:** An occlusion patch needed only a feature flag check, but the
+  old patch also contained a version check that upstream intentionally removed.
+  Mechanically preserving the old patch code re-added the removed check.
+
+### Lesson: Finish the Adaptation at Conflict Time
+
+- **Trigger:** A patch conflict involves an upstream API removal or replacement
+- **Strategy:** When resolving the conflict, fully adapt the patch to use the
+  new API in the same commit. Don't remove the old code and leave behind stale
+  references that will "be fixed in Phase Two." Each patch fix commit should be
+  a complete resolution.
+- **Evidence:** A safestorage patch conflicted because Chromium removed Keychain V1.
+  The conflict was resolved by removing V1 hunks, but the remaining code still
+  called V1 methods (`FindGenericPassword` with 3 args, `ItemDelete` with
+  `SecKeychainItemRef`). These should have been adapted to V2 APIs in the same
+  commit, not deferred.
+
 ## Common Failure Patterns
 
 | Pattern | Cause | Solution |

.claude/skills/electron-chromium-upgrade/references/phase-one-commit-guidelines.md

@@ -4,19 +4,65 @@ Only follow these instructions if there are uncommitted changes to `patches/` af
 
 Ignore other instructions about making commit messages, our guidelines are CRITICALLY IMPORTANT and must be followed.
 
-## Atomic Commits
+## Each Commit Must Be Complete
 
-For each fix made to a patch, create a separate commit:
+When resolving a patch conflict, fully adapt the patch to the new upstream code in the same commit. If the upstream change removes an API the patch uses, update the patch to use the replacement API now — don't leave stale references knowing they'll need fixing later. The goal is that each commit represents a finished resolution, not a partial one that defers known work to a future phase.
+
+## Commit Message Style
+
+**Titles** follow the 60/80-character guideline: simple changes fit within 60 characters, otherwise the limit is 80 characters.
+
+Always include a `Co-Authored-By` trailer identifying the AI model that assisted (e.g., `Co-Authored-By: <AI model attribution>`).
+
+### Patch conflict fixes
+
+Use `fix(patch):` prefix. The title should name the upstream change, not your response to it:
 
 ```
-fix(patch-conflict): {concise title}
-
-{Brief explanation, 1-2 paragraphs max}
+fix(patch): {topic headline}
 
 Ref: {Chromium CL link}
+
+Co-Authored-By: <AI model attribution>
 ```
 
-IMPORTANT: Ensure that any changes made to patch content as a result of a change in Chromium is committed individually. Each change should have it's own commit message and it's own REF.
+Only add a description body if it provides clarity beyond the title. For straightforward context drift or simple API renames, the title + Ref is sufficient.
+
+Examples:
+- `fix(patch): constant moved to header`
+- `fix(patch): headless mode refactor upstream`
+- `fix(patch): V1 Keychain removal`
+
+### Upstreamed patch removal
+
+When patches are no longer needed (applied cleanly with "already applied" or confirmed upstreamed), group ALL removals into a single commit:
+
+```
+chore: remove upstreamed patch
+```
+
+or (if multiple):
+
+```
+chore: remove upstreamed patches
+```
+
+If the patch file did NOT contain a `Reviewed-on: https://chromium-review.googlesource.com/c/chromium/...` link, add a `Ref:` in the commit. If it did (i.e. cherry-picks), no `Ref:` is needed.
+
+### Trivial patch updates
+
+After all fix commits, stage remaining trivial changes (index, line numbers, context only):
+
+```bash
+git add patches
+git commit -m "chore: update patches (trivial only)"
+```
+
+**Conflict resolution can produce trivial results.** A `git am` conflict doesn't always mean the patch content changed — context drift alone can cause a conflict. After resolving and exporting, inspect the patch diff: if only index hashes, line numbers, and context lines changed (not the patch's own `+`/`-` lines), it's trivial and belongs here, not in a `fix(patch):` commit.
+
+## Atomic Commits
+
+Each patch conflict fix gets its own commit with its own Ref.
 
 IMPORTANT: Try really hard to find the CL reference per the instructions below. Each change you made should in theory have been in response to a change made in Chromium that you identified or can identify. Try for a while to identify and include the ref in the commit message. Do not give up easily.
 
@@ -30,23 +76,27 @@ Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/XXXXXXX
 
 If no CL found after searching: `Ref: Unable to locate CL`
 
-## Final Cleanup
+## Example Commits
 
-After all fix commits, stage remaining changes:
-
-```bash
-git add patches
-git commit -m "chore: update patch hunk headers"
-```
-
-## Example Commit
+### Patch conflict fix (simple — title is sufficient)
 
 ```
-fix(patch-conflict): update web_contents_impl.cc context for navigation refactor
+fix(patch): constant moved to header
 
-The upstream navigation code was refactored to use NavigationRequest directly
-instead of going through NavigationController. Updated surrounding context
-to match new code structure.
+Ref: https://chromium-review.googlesource.com/c/chromium/src/+/7536483
 
-Ref: https://chromium-review.googlesource.com/c/chromium/src/+/1234567
-```
+Co-Authored-By: <AI model attribution>
+```
+
+### Patch conflict fix (complex — description adds value)
+
+```
+fix(patch): V1 Keychain removal
+
+Upstream deleted the V1 Keychain API. Removed V1 hunks and adapted
+keychain_password_mac.mm to use KeychainV2 APIs.
+
+Ref: https://chromium-review.googlesource.com/c/chromium/src/+/7540447
+
+Co-Authored-By: <AI model attribution>
+```

.claude/skills/electron-chromium-upgrade/references/phase-two-commit-guidelines.md

@@ -4,41 +4,37 @@ Only follow these instructions if there are uncommitted changes in the Electron
 
 Ignore other instructions about making commit messages, our guidelines are CRITICALLY IMPORTANT and must be followed.
 
+## Commit Message Style
+
+**Titles** follow the 60/80-character guideline: simple changes fit within 60 characters, otherwise the limit is 80 characters. Exception: upstream Chromium CL titles are used verbatim even if longer.
+
+Always include a `Co-Authored-By` trailer identifying the AI model that assisted (e.g., `Co-Authored-By: <AI model attribution>`).
+
 ## Two Commit Types
 
 ### For Electron Source Changes (shell/, electron/, etc.)
 
 ```
-{CL-Number}: {concise description of API change}
-
-{Brief explanation of what upstream changed and how Electron was adapted}
+{CL-Number}: {upstream CL's original title}
 
 Ref: {Chromium CL link}
+
+Co-Authored-By: <AI model attribution>
 ```
 
-IMPORTANT: Ensure that any change made to electron as a result of a change in Chromium is committed individually. Each change should have it's own commit message and it's own REF. Logically grouped into commits that make sense rather than one giant commit.
+Use the **upstream CL's original commit title** — do not paraphrase or rewrite it. To find it: `git log -1 --format=%s <chromium-commit-hash>`.
 
-IMPORTANT: Try really hard to find the CL reference per the instructions below. Each change you made should in theory have been in response to a change made in Chromium that you identified or can identify. Try for a while to identify and include the ref in the commit message. Do not give up easily.
+Only add a description body if it provides clarity beyond what the title already says (e.g., when Electron's adaptation is non-obvious). For simple renames, method additions, or straightforward API updates, the title + Ref link is sufficient.
 
-You may include multiple "Ref" links if required.
+Each change should have its own commit and its own Ref. Logically group into commits that make sense rather than one giant commit. You may include multiple "Ref" links if required.
 
-For a CL link in the format `https://chromium-review.googlesource.com/c/chromium/src/+/2958369` the "CL-Number" is `2958369`
+For a CL link in the format `https://chromium-review.googlesource.com/c/chromium/src/+/2958369` the "CL-Number" is `2958369`.
+
+IMPORTANT: Try really hard to find the CL reference. Each change you made should in theory have been in response to a change in Chromium. Do not give up easily.
 
 ### For Patch Updates (patches/chromium/*.patch)
 
-Use the same fixup workflow as Phase One:
-1. Fix in Chromium source tree
-2. Fixup commit + rebase
-3. Export with `e patches chromium`
-4. Commit the patch file:
-
-```
-fix(patch-update): {concise description}
-
-{Brief explanation}
-
-Ref: {Chromium CL link}
-```
+Use the same fixup workflow as Phase One and follow `references/phase-one-commit-guidelines.md` for the commit message format (`fix(patch):` prefix, topic style).
 
 ## Dependent Patch Header Updates
 
@@ -46,37 +42,43 @@ After any patch modification, check for other affected patches:
 
 ```bash
 git status
-# If other .patch files show as modified with only hunk header changes:
+# If other .patch files show as modified with only index, line number, and context changes:
 git add patches/
-git commit -m "chore: update patch hunk headers"
+git commit -m "chore: update patches (trivial only)"
 ```
 
 ## Finding CL References
 
 Use git log or git blame on Chromium source files. Look for:
 
+```
 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/XXXXXXX
+```
 
-If no CL found after searching: Ref: Unable to locate CL
+If no CL found after searching: `Ref: Unable to locate CL`
 
 ## Example Commits
 
-### Electron Source Fix
+### Electron Source Fix (simple — title is self-explanatory)
 
-fix: update GetPlugins to GetPluginsAsync for API change
+```
+7535923: Rename ozone buildflags
 
-The upstream Chromium API changed:
-- Old: GetPlugins(callback) - took a callback
-- New: GetPluginsAsync(callback) - async version takes a callback
+Ref: https://chromium-review.googlesource.com/c/chromium/src/+/7535923
 
-Ref: https://chromium-review.googlesource.com/c/chromium/src/+/1234567
+Co-Authored-By: <AI model attribution>
+```
 
-### Patch Fix
+### Electron Source Fix (complex — description adds value)
 
-fix(patch-conflict): update picture-in-picture for gesture handling refactor
+```
+7534194: Convert some functions in ui::Clipboard to async
 
-Upstream added new gesture handling code that accesses live caption dialog.
-The live caption functionality is disabled in Electron's patch, so wrapped
-the new code in #if 0 guards to match existing pattern.
+Adapted ExtractCustomPlatformNames calls to use RunLoop pattern
+consistent with existing ReadImage implementation, since upstream
+converted the API from synchronous return to callback-based.
 
-Ref: https://chromium-review.googlesource.com/c/chromium/src/+/7654321
+Ref: https://chromium-review.googlesource.com/c/chromium/src/+/7534194
+
+Co-Authored-By: <AI model attribution>
+```

.github/actions/build-electron/action.yml

@@ -98,7 +98,7 @@ runs:
         # Upload build stats to Datadog
         if ($env:DD_API_KEY) {
           try {
-            npx node electron\script\build-stats.mjs out\Default\siso.exe.INFO --upload-stats
+            npx node electron\script\build-stats.mjs out\Default\siso.exe.INFO --upload-stats ; $LASTEXITCODE = 0
           } catch {
             Write-Host "Build stats upload failed, continuing..."
           }

.github/actions/install-build-tools/action.yml

@@ -15,7 +15,7 @@ runs:
         git config --global core.preloadindex true
         git config --global core.longpaths true
       fi
-      export BUILD_TOOLS_SHA=4430e4a505e0f4fa2a41b707a10a36f780bbdd26
+      export BUILD_TOOLS_SHA=a0cc95a1884a631559bcca0c948465b725d9295a
       npm i -g @electron/build-tools
       # Update depot_tools to ensure python
       e d update_depot_tools

.github/copilot-instructions.md

@@ -0,0 +1,122 @@
+# Copilot Instructions for Electron
+
+## Build System
+
+Electron uses `@electron/build-tools` (`e` CLI). Install with `npm i -g @electron/build-tools`.
+
+```bash
+e sync              # Fetch sources and apply patches
+e build             # Build Electron (GN + Ninja)
+e build -k 999      # Build, continuing through errors
+e start             # Run built Electron
+e start --version   # Verify Electron launches
+e test              # Run full test suite
+e debug             # Run in debugger (lldb on macOS, gdb on Linux)
+```
+
+### Linting
+
+```bash
+npm run lint              # Run all linters (JS, C++, Python, GN, docs)
+npm run lint:js           # JavaScript/TypeScript only
+npm run lint:clang-format # C++ formatting only
+npm run lint:cpp          # C++ linting only
+npm run lint:docs         # Documentation only
+```
+
+### Running a Single Test
+
+```bash
+npm run test -- -g "pattern"   # Run tests matching a regex pattern
+# Example: npm run test -- -g "ipc"
+```
+
+### Running a Single Node.js Test
+
+```bash
+node script/node-spec-runner.js parallel/test-crypto-keygen
+```
+
+## Architecture
+
+Electron embeds Chromium (rendering) and Node.js (backend) to enable desktop apps with web technologies. The parent directory (`../`) is the Chromium source tree.
+
+### Process Model
+
+Electron has two primary process types, mirroring Chromium:
+
+- **Main process** (`shell/browser/` + `lib/browser/`): Controls app lifecycle, creates windows, system APIs
+- **Renderer process** (`shell/renderer/` + `lib/renderer/`): Runs web content in BrowserWindows
+
+### Native ↔ JavaScript Bridge
+
+Each API is implemented as a C++/JS pair:
+
+- C++ side: `shell/browser/api/electron_api_{name}.cc/.h` — uses `gin::Wrappable` and `ObjectTemplateBuilder`
+- JS side: `lib/browser/api/{name}.ts` — exports the module, registered in `lib/browser/api/module-list.ts`
+- Binding: `NODE_LINKED_BINDING_CONTEXT_AWARE(electron_browser_{name}, Initialize)` in C++ and registered in `shell/common/node_bindings.cc`
+- Type declaration: `typings/internal-ambient.d.ts` maps `process._linkedBinding('electron_browser_{name}')`
+
+### Patches System
+
+Electron patches upstream dependencies (Chromium, Node.js, V8, etc.) rather than forking them. Patches live in `patches/` organized by target, with `patches/config.json` mapping directories to repos.
+
+```text
+patches/{target}/*.patch  →  [e sync]   →  target repo commits
+                          ←  [e patches] ←
+```
+
+Key rules:
+
+- Fix existing patches rather than creating new ones
+- Preserve original authorship in TODO comments — never change `TODO(name)` assignees
+- Each patch commit message must explain why the patch exists
+- After modifying patches, run `e patches {target}` to export
+
+When working on the `roller/chromium/main` branch for Chromium upgrades, use `e sync --3` for 3-way merge conflict resolution.
+
+## Conventions
+
+### File Naming
+
+- JS/TS files: kebab-case (`file-name.ts`)
+- C++ files: snake_case with `electron_api_` prefix (`electron_api_safe_storage.cc`)
+- Test files: `api-{module-name}-spec.ts` in `spec/`
+- Source file lists are maintained in `filenames.gni` (with platform-specific sections)
+
+### JavaScript/TypeScript
+
+- Semicolons required (`"semi": ["error", "always"]`)
+- `const` and `let` only (no `var`)
+- Arrow functions preferred
+- Import order enforced: `@electron/internal` → `@electron` → `electron` → external → builtin → relative
+- API naming: `PascalCase` for classes (`BrowserWindow`), `camelCase` for module APIs (`globalShortcut`)
+- Prefer getters/setters over jQuery-style `.text([text])` patterns
+
+### C++
+
+- Follows Chromium coding style, enforced by `clang-format` and `clang-tidy`
+- Uses Chromium abstractions (`base::`, `content::`, etc.)
+- Header guards: `#ifndef ELECTRON_SHELL_BROWSER_API_ELECTRON_API_{NAME}_H_`
+- Platform-specific files: `_mac.mm`, `_win.cc`, `_linux.cc`
+
+### Testing
+
+- Framework: Mocha + Chai + Sinon
+- Test helpers in `spec/lib/` (e.g., `spec-helpers.ts`, `window-helpers.ts`)
+- Use `defer()` from spec-helpers for cleanup, `closeAllWindows()` for window teardown
+- Tests import from `electron/main` or `electron/renderer`
+
+### Documentation
+
+- API docs in `docs/api/` as Markdown, parsed by `@electron/docs-parser` to generate `electron.d.ts`
+- API history tracked via YAML blocks in HTML comments within doc files
+- Docs must pass `npm run lint:docs`
+
+### Build Configuration
+
+- `BUILD.gn`: Main GN build config
+- `buildflags/buildflags.gni`: Feature flags (PDF viewer, extensions, spellchecker)
+- `build/args/`: Build argument profiles (`testing.gn`, `release.gn`, `all.gn`)
+- `DEPS`: Dependency versions and checkout paths
+- `chromium_src/`: Chromium source file overrides (compiled instead of originals)

.github/problem-matchers/markdownlint.json

@@ -0,0 +1,16 @@
+{
+  "problemMatcher": [
+    {
+      "owner": "markdownlint",
+      "pattern": [
+        {
+          "regexp": "^(.+):(\\d+):(\\d+)\\s+(.*)$",
+          "file": 1,
+          "line": 2,
+          "column": 3,
+          "message": 4
+        }
+      ]
+    }
+  ]
+}

.github/workflows/issue-commented.yml

@@ -1,4 +1,4 @@
-name: Issue Commented
+name: Issue / Pull Request Commented
 
 on:
   issue_comment:
@@ -8,16 +8,16 @@ on:
 permissions: {}
 
 jobs:
-  issue-commented:
+  blocked-issue-commented:
     name: Remove blocked/{need-info,need-repro} on comment
-    if: ${{ (contains(github.event.issue.labels.*.name, 'blocked/need-repro') || contains(github.event.issue.labels.*.name, 'blocked/need-info ❌')) && github.event.comment.user.type != 'Bot' }}
-    runs-on: ubuntu-latest
+    if: ${{ !github.event.issue.pull_request && (contains(github.event.issue.labels.*.name, 'blocked/need-repro') || contains(github.event.issue.labels.*.name, 'blocked/need-info ❌')) && github.event.comment.user.type != 'Bot' }}
+    runs-on: ubuntu-slim
     steps:
       - name: Get author association
         id: get-author-association
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        run: |
+        run: &get-author-association |
           AUTHOR_ASSOCIATION=$(gh api /repos/electron/electron/issues/comments/${{ github.event.comment.id }} --jq '.author_association')
           echo "author_association=$AUTHOR_ASSOCIATION" >> "$GITHUB_OUTPUT"
       - name: Generate GitHub App token
@@ -33,3 +33,56 @@ jobs:
           ISSUE_URL: ${{ github.event.issue.html_url }}
         run: |
           gh issue edit $ISSUE_URL --remove-label 'blocked/need-repro','blocked/need-info ❌'
+
+  pr-reviewer-requested:
+    name: Maintainer requested reviewer on PR
+    if: ${{ github.event.issue.pull_request && startsWith(github.event.comment.body, '/request-review') && github.event.comment.user.type != 'Bot' }}
+    runs-on: ubuntu-slim
+    steps:
+      - name: Get author association
+        id: get-author-association
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: *get-author-association
+      - name: Generate GitHub App token
+        uses: electron/github-app-auth-action@e14e47722ed120360649d0789e25b9baece12725 # v2.0.0
+        if: ${{ contains(fromJSON('["MEMBER", "OWNER"]'), steps.get-author-association.outputs.author_association) }}
+        id: generate-token
+        with:
+          creds: ${{ secrets.ISSUE_TRIAGE_GH_APP_CREDS }}
+      - name: Request reviewer
+        if: ${{ contains(fromJSON('["MEMBER", "OWNER"]'), steps.get-author-association.outputs.author_association) }}
+        env:
+          GITHUB_TOKEN: ${{ steps.generate-token.outputs.token }}
+          PR_URL: ${{ github.event.issue.html_url }}
+          COMMENT_BODY: ${{ github.event.comment.body }}
+        run: |
+          RAW=$(echo "$COMMENT_BODY" | head -n 1 | sed 's|/request-review\s*||' | xargs)
+
+          if [ -z "$RAW" ]; then
+            echo "::warning::No username provided. Usage: /request-review <username>[,<username>,...]"
+            exit 0
+          fi
+
+          IFS=',' read -ra USERS <<< "$RAW"
+          for USER in "${USERS[@]}"; do
+            NAME=$(echo "$USER" | sed 's/@//g' | xargs)
+            if [ -z "$NAME" ]; then
+              continue
+            fi
+
+            # Strip "electron/" prefix if present to get the bare name
+            BARE_NAME=$(echo "$NAME" | sed 's|^electron/||')
+
+            # If the original name contained "electron/" or looks like a team slug, treat as team
+            if [ "$NAME" != "$BARE_NAME" ]; then
+              gh pr edit $PR_URL --add-reviewer "electron/$BARE_NAME"
+            else
+              if ! gh api /orgs/electron/public_members/$BARE_NAME --silent > /dev/null 2>&1; then
+                echo "::warning::$BARE_NAME is not a public member of the electron organization."
+                continue
+              fi
+
+              gh pr edit $PR_URL --add-reviewer "$BARE_NAME"
+            fi
+          done

.github/workflows/issue-labeled.yml

@@ -75,7 +75,7 @@ jobs:
           creds: ${{ secrets.ISSUE_TRIAGE_GH_APP_CREDS }}
       - name: Create comment
         if: ${{ steps.check-for-comment.outputs.SHOULD_COMMENT }}
-        uses: actions-cool/issues-helper@e2ff99831a4f13625d35064e2b3dfe65c07a0396 # v3.7.5
+        uses: actions-cool/issues-helper@71b62d7da76e59ff7b193904feb6e77d4dbb2777 # v3.7.6
         with:
           actions: 'create-comment'
           token: ${{ steps.generate-token.outputs.token }}

.github/workflows/issue-opened.yml

@@ -146,7 +146,7 @@ jobs:
             }
       - name: Create unsupported major comment
         if: ${{ steps.add-labels.outputs.unsupportedMajor }}
-        uses: actions-cool/issues-helper@e2ff99831a4f13625d35064e2b3dfe65c07a0396 # v3.7.5
+        uses: actions-cool/issues-helper@71b62d7da76e59ff7b193904feb6e77d4dbb2777 # v3.7.6
         with:
           actions: 'create-comment'
           token: ${{ steps.generate-token.outputs.token }}

.github/workflows/linux-publish.yml

@@ -46,6 +46,7 @@ jobs:
   publish-x64:
     uses: ./.github/workflows/pipeline-segment-electron-publish.yml
     permissions:
+      artifact-metadata: write
       attestations: write
       contents: read
       id-token: write
@@ -65,6 +66,7 @@ jobs:
   publish-arm:
     uses: ./.github/workflows/pipeline-segment-electron-publish.yml
     permissions:
+      artifact-metadata: write
       attestations: write
       contents: read
       id-token: write
@@ -84,6 +86,7 @@ jobs:
   publish-arm64:
     uses: ./.github/workflows/pipeline-segment-electron-publish.yml
     permissions:
+      artifact-metadata: write
       attestations: write
       contents: read
       id-token: write

.github/workflows/macos-publish.yml

@@ -50,6 +50,7 @@ jobs:
   publish-x64-darwin:
     uses: ./.github/workflows/pipeline-segment-electron-publish.yml
     permissions:
+      artifact-metadata: write
       attestations: write
       contents: read
       id-token: write
@@ -69,6 +70,7 @@ jobs:
   publish-x64-mas:
     uses: ./.github/workflows/pipeline-segment-electron-publish.yml
     permissions:
+      artifact-metadata: write
       attestations: write
       contents: read
       id-token: write
@@ -88,6 +90,7 @@ jobs:
   publish-arm64-darwin:
     uses: ./.github/workflows/pipeline-segment-electron-publish.yml
     permissions:
+      artifact-metadata: write
       attestations: write
       contents: read
       id-token: write
@@ -107,6 +110,7 @@ jobs:
   publish-arm64-mas:
     uses: ./.github/workflows/pipeline-segment-electron-publish.yml
     permissions:
+      artifact-metadata: write
       attestations: write
       contents: read
       id-token: write

.github/workflows/pipeline-electron-lint.yml

@@ -65,9 +65,11 @@ jobs:
         curl -sL "https://chromium.googlesource.com/chromium/src/+/${chromium_revision}/buildtools/DEPS?format=TEXT" | base64 -d > src/buildtools/DEPS
 
         gclient sync --spec="solutions=[{'name':'src/buildtools','url':None,'deps_file':'DEPS','custom_vars':{'process_deps':True},'managed':False}]"
-    - name: Add ESLint problem matcher
+    - name: Add problem matchers
       shell: bash
-      run: echo "::add-matcher::src/electron/.github/problem-matchers/eslint-stylish.json"
+      run: |
+        echo "::add-matcher::src/electron/.github/problem-matchers/eslint-stylish.json"
+        echo "::add-matcher::src/electron/.github/problem-matchers/markdownlint.json"
     - name: Run Lint
       shell: bash
       run: |

.github/workflows/pipeline-segment-electron-publish.yml

@@ -93,6 +93,7 @@ jobs:
         shell: bash
     runs-on: ${{ inputs.build-runs-on }}
     permissions:
+      artifact-metadata: write
       attestations: write
       contents: read
       id-token: write

.github/workflows/pipeline-segment-electron-test.yml

@@ -191,18 +191,12 @@ jobs:
       run: |
         cd src/out/Default
         unzip -:o dist.zip
-    - name: Import & Trust Self-Signed Codesigning Cert on MacOS
-      if: ${{ inputs.target-platform == 'macos' }}
-      run: |
-        cd src/electron
-        ./script/codesign/generate-identity.sh
-    - name: Sign Electron.app for macOS tests
-      if: ${{ inputs.target-platform == 'macos' }}
-      run: |
-        identity=$(src/electron/script/codesign/get-trusted-identity.sh)
-        if [ -n "$identity" ]; then
-          codesign -s "$identity" --deep --force src/out/Default/Electron.app
-        fi
+    #- name: Import & Trust Self-Signed Codesigning Cert on MacOS
+    #  if: ${{ inputs.target-platform == 'macos' && inputs.target-arch == 'x64' }}
+    #  run: |
+    #    sudo security authorizationdb write com.apple.trust-settings.admin allow
+    #    cd src/electron
+    #    ./script/codesign/generate-identity.sh
 
     - name: Run Electron Tests
       shell: bash

.github/workflows/pull-request-labeled.yml

@@ -56,7 +56,7 @@ jobs:
       with:
         creds: ${{ secrets.ISSUE_TRIAGE_GH_APP_CREDS }}
     - name: Create comment
-      uses: actions-cool/issues-helper@e2ff99831a4f13625d35064e2b3dfe65c07a0396 # v3.7.5
+      uses: actions-cool/issues-helper@71b62d7da76e59ff7b193904feb6e77d4dbb2777 # v3.7.6
       with:
         actions: 'create-comment'
         token: ${{ steps.generate-token.outputs.token }}

.github/workflows/scorecards.yml

@@ -51,6 +51,6 @@ jobs:
 
       # Upload the results to GitHub's code scanning dashboard.
       - name: "Upload to code-scanning"
-        uses: github/codeql-action/upload-sarif@45cbd0c69e560cd9e7cd7f8c32362050c9b7ded2 # v3.29.5
+        uses: github/codeql-action/upload-sarif@89a39a4e59826350b863aa6b6252a07ad50cf83e # v3.29.5
         with:
           sarif_file: results.sarif

.github/workflows/stale.yml

@@ -18,7 +18,7 @@ jobs:
         id: generate-token
         with:
           creds: ${{ secrets.ISSUE_TRIAGE_GH_APP_CREDS }}
-      - uses: actions/stale@997185467fa4f803885201cee163a9f38240193d # tag: v10.1.1
+      - uses: actions/stale@b5d41d4e1d5dceea10e7104786b73624c18a190f # tag: v10.2.0
         with:
           repo-token: ${{ steps.generate-token.outputs.token }}
           days-before-stale: 90
@@ -42,7 +42,7 @@ jobs:
         id: generate-token
         with:
           creds: ${{ secrets.ISSUE_TRIAGE_GH_APP_CREDS }}
-      - uses: actions/stale@997185467fa4f803885201cee163a9f38240193d # tag: v10.1.1
+      - uses: actions/stale@b5d41d4e1d5dceea10e7104786b73624c18a190f # tag: v10.2.0
         with:
           repo-token: ${{ steps.generate-token.outputs.token }}
           days-before-stale: -1

.github/workflows/update-website-docs.yml

@@ -31,7 +31,7 @@ jobs:
             echo "isLatestRelease=false" >> $GITHUB_OUTPUT
           fi
       - name: Trigger website docs update
-        if: ${{ steps.check-if-latest-release.outputs.isLatestRelease }}
+        if: ${{ steps.check-if-latest-release.outputs.isLatestRelease == 'true' }}
         env:
           GH_REPO: electron/website
           GH_TOKEN: ${{ fromJSON(steps.secret-service.outputs.secrets).WEBSITE_DOCS_UPDATER_APP_TOKEN }}

.github/workflows/windows-publish.yml

@@ -54,6 +54,7 @@ jobs:
   publish-x64-win:
     uses: ./.github/workflows/pipeline-segment-electron-publish.yml
     permissions:
+      artifact-metadata: write
       attestations: write
       contents: read
       id-token: write
@@ -72,6 +73,7 @@ jobs:
   publish-arm64-win:
     uses: ./.github/workflows/pipeline-segment-electron-publish.yml
     permissions:
+      artifact-metadata: write
       attestations: write
       contents: read
       id-token: write
@@ -90,6 +92,7 @@ jobs:
   publish-x86-win:
     uses: ./.github/workflows/pipeline-segment-electron-publish.yml
     permissions:
+      artifact-metadata: write
       attestations: write
       contents: read
       id-token: write

BUILD.gn

@@ -321,33 +321,12 @@ grit("resources") {
     "grit/electron_resources.h",
     "electron_resources.pak",
   ]
-  if (translate_genders) {
-    outputs += [
-      "electron_resources_MASCULINE.pak",
-      "electron_resources_FEMININE.pak",
-      "electron_resources_NEUTER.pak",
-    ]
-  }
-
-  foreach(locale, all_chrome_locales) {
-    outputs += [ "electron_strings_$locale.pak" ]
-    if (translate_genders) {
-      outputs += [
-        "electron_strings_${locale}_MASCULINE.pak",
-        "electron_strings_${locale}_FEMININE.pak",
-        "electron_strings_${locale}_NEUTER.pak",
-      ]
-    }
-  }
 
   # Mojo manifest overlays are generated.
   grit_flags = [
     "-E",
     "target_gen_dir=" + rebase_path(target_gen_dir, root_build_dir),
   ]
-  if (translate_genders) {
-    grit_flags += [ "--translate-genders" ]
-  }
 
   deps = [ ":copy_shell_devtools_discovery_page" ]
 
@@ -471,7 +450,6 @@ source_set("electron_lib") {
     "//chrome:strings",
     "//chrome/app:command_ids",
     "//chrome/app/resources:platform_locale_settings",
-    "//chrome/common/notifications",
     "//components/autofill/core/common:features",
     "//components/certificate_transparency",
     "//components/compose:buildflags",
@@ -618,6 +596,7 @@ source_set("electron_lib") {
     use_libcxx_modules = false
 
     deps += [
+      "//components/os_crypt/async/browser:keychain_key_provider",
       "//components/os_crypt/common:keychain_password_mac",
       "//components/remote_cocoa/app_shim",
       "//components/remote_cocoa/browser",
@@ -640,7 +619,6 @@ source_set("electron_lib") {
       "SecurityInterface.framework",
       "ServiceManagement.framework",
       "StoreKit.framework",
-      "UserNotifications.framework",
     ]
 
     weak_frameworks = [ "QuickLookThumbnailing.framework" ]
@@ -681,6 +659,9 @@ source_set("electron_lib") {
       ":libnotify_loader",
       "//build/config/linux/gtk",
       "//components/crash/content/browser",
+      "//components/os_crypt/async/browser:freedesktop_secret_key_provider",
+      "//components/os_crypt/async/browser:posix_key_provider",
+      "//components/os_crypt/async/browser:secret_portal_key_provider",
       "//dbus",
       "//device/bluetooth",
       "//third_party/crashpad/crashpad/client",
@@ -721,6 +702,7 @@ source_set("electron_lib") {
     deps += [
       "//components/app_launch_prefetch",
       "//components/crash/core/app:crash_export_thunks",
+      "//components/os_crypt/async/browser:dpapi_key_provider",
       "//third_party/libxml:xml_writer",
       "//ui/wm",
       "//ui/wm/public",

CLAUDE.md

@@ -155,6 +155,10 @@ e test                    # Run full test suite
 
 When working on the `roller/chromium/main` branch to upgrade Chromium activate the "Electron Chromium Upgrade" skill.
 
+## Pull Requests
+
+PR bodies must always include a `Notes:` section as the **last line** of the body. This is a consumer-facing release note for Electron app developers — describe the user-visible fix or change, not internal implementation details. Use `Notes: none` if there is no user-facing change.
+
 ## Code Style
 
 **C++:** Follows Chromium style, enforced by clang-format

DEPS

@@ -2,9 +2,9 @@ gclient_gn_args_from = 'src'
 
 vars = {
   'chromium_version':
-    '146.0.7650.0',
+    '147.0.7699.0',
   'node_version':
-    'v24.13.0',
+    'v24.14.0',
   'nan_version':
     '675cefebca42410733da8a454c8d9391fcebfbc2',
   'squirrel.mac_version':

build/electron_paks.gni

@@ -183,7 +183,6 @@ template("electron_paks") {
       "${root_gen_dir}/components/strings/components_locale_settings_",
       "${root_gen_dir}/components/strings/components_strings_",
       "${root_gen_dir}/device/bluetooth/strings/bluetooth_strings_",
-      "${root_gen_dir}/electron/electron_strings_",
       "${root_gen_dir}/extensions/strings/extensions_strings_",
       "${root_gen_dir}/services/strings/services_strings_",
       "${root_gen_dir}/third_party/blink/public/strings/blink_strings_",
@@ -200,7 +199,6 @@ template("electron_paks") {
       "//components/strings:components_locale_settings",
       "//components/strings:components_strings",
       "//device/bluetooth/strings",
-      "//electron:resources",
       "//extensions/strings",
       "//services/strings",
       "//third_party/blink/public/strings",

build/electron_resources.grd

@@ -9,189 +9,10 @@
       <emit emit_type='prepend'></emit>
     </output>
     <output filename="electron_resources.pak" type="data_package" />
-    <output filename="electron_strings_af.pak" type="data_package" lang="af" />
-    <output filename="electron_strings_am.pak" type="data_package" lang="am" />
-    <output filename="electron_strings_ar.pak" type="data_package" lang="ar" />
-    <output filename="electron_strings_as.pak" type="data_package" lang="as" />
-    <output filename="electron_strings_az.pak" type="data_package" lang="az" />
-    <output filename="electron_strings_be.pak" type="data_package" lang="be" />
-    <output filename="electron_strings_bg.pak" type="data_package" lang="bg" />
-    <output filename="electron_strings_bn.pak" type="data_package" lang="bn" />
-    <output filename="electron_strings_bs.pak" type="data_package" lang="bs" />
-    <output filename="electron_strings_ca.pak" type="data_package" lang="ca" />
-    <output filename="electron_strings_cs.pak" type="data_package" lang="cs" />
-    <output filename="electron_strings_cy.pak" type="data_package" lang="cy" />
-    <output filename="electron_strings_da.pak" type="data_package" lang="da" />
-    <output filename="electron_strings_de.pak" type="data_package" lang="de" />
-    <output filename="electron_strings_el.pak" type="data_package" lang="el" />
-    <output filename="electron_strings_en-GB.pak" type="data_package" lang="en-GB" />
-    <output filename="electron_strings_en-US.pak" type="data_package" lang="en" />
-    <output filename="electron_strings_es-419.pak" type="data_package" lang="es-419" />
-    <output filename="electron_strings_es.pak" type="data_package" lang="es" />
-    <output filename="electron_strings_et.pak" type="data_package" lang="et" />
-    <output filename="electron_strings_eu.pak" type="data_package" lang="eu" />
-    <output filename="electron_strings_fa.pak" type="data_package" lang="fa" />
-    <output filename="electron_strings_fi.pak" type="data_package" lang="fi" />
-    <output filename="electron_strings_fil.pak" type="data_package" lang="fil" />
-    <output filename="electron_strings_fr-CA.pak" type="data_package" lang="fr-CA" />
-    <output filename="electron_strings_fr.pak" type="data_package" lang="fr" />
-    <output filename="electron_strings_gl.pak" type="data_package" lang="gl" />
-    <output filename="electron_strings_gu.pak" type="data_package" lang="gu" />
-    <output filename="electron_strings_hi.pak" type="data_package" lang="hi" />
-    <output filename="electron_strings_hr.pak" type="data_package" lang="hr" />
-    <output filename="electron_strings_hu.pak" type="data_package" lang="hu" />
-    <output filename="electron_strings_hy.pak" type="data_package" lang="hy" />
-    <output filename="electron_strings_id.pak" type="data_package" lang="id" />
-    <output filename="electron_strings_is.pak" type="data_package" lang="is" />
-    <output filename="electron_strings_it.pak" type="data_package" lang="it" />
-    <output filename="electron_strings_he.pak" type="data_package" lang="he" />
-    <output filename="electron_strings_ja.pak" type="data_package" lang="ja" />
-    <output filename="electron_strings_ka.pak" type="data_package" lang="ka" />
-    <output filename="electron_strings_kk.pak" type="data_package" lang="kk" />
-    <output filename="electron_strings_km.pak" type="data_package" lang="km" />
-    <output filename="electron_strings_kn.pak" type="data_package" lang="kn" />
-    <output filename="electron_strings_ko.pak" type="data_package" lang="ko" />
-    <output filename="electron_strings_ky.pak" type="data_package" lang="ky" />
-    <output filename="electron_strings_lo.pak" type="data_package" lang="lo" />
-    <output filename="electron_strings_lt.pak" type="data_package" lang="lt" />
-    <output filename="electron_strings_lv.pak" type="data_package" lang="lv" />
-    <output filename="electron_strings_mk.pak" type="data_package" lang="mk" />
-    <output filename="electron_strings_ml.pak" type="data_package" lang="ml" />
-    <output filename="electron_strings_mn.pak" type="data_package" lang="mn" />
-    <output filename="electron_strings_mr.pak" type="data_package" lang="mr" />
-    <output filename="electron_strings_ms.pak" type="data_package" lang="ms" />
-    <output filename="electron_strings_my.pak" type="data_package" lang="my" />
-    <output filename="electron_strings_ne.pak" type="data_package" lang="ne" />
-    <output filename="electron_strings_nl.pak" type="data_package" lang="nl" />
-    <!-- The translation console uses 'no' for Norwegian Bokmål. It should
-         be 'nb'. -->
-    <output filename="electron_strings_nb.pak" type="data_package" lang="no" />
-    <output filename="electron_strings_or.pak" type="data_package" lang="or" />
-    <output filename="electron_strings_pa.pak" type="data_package" lang="pa" />
-    <output filename="electron_strings_pl.pak" type="data_package" lang="pl" />
-    <output filename="electron_strings_pt-BR.pak" type="data_package" lang="pt-BR" />
-    <output filename="electron_strings_pt-PT.pak" type="data_package" lang="pt-PT" />
-    <output filename="electron_strings_ro.pak" type="data_package" lang="ro" />
-    <output filename="electron_strings_ru.pak" type="data_package" lang="ru" />
-    <output filename="electron_strings_si.pak" type="data_package" lang="si" />
-    <output filename="electron_strings_sk.pak" type="data_package" lang="sk" />
-    <output filename="electron_strings_sl.pak" type="data_package" lang="sl" />
-    <output filename="electron_strings_sq.pak" type="data_package" lang="sq" />
-    <output filename="electron_strings_sr-Latn.pak" type="data_package" lang="sr-Latn" />
-    <output filename="electron_strings_sr.pak" type="data_package" lang="sr" />
-    <output filename="electron_strings_sv.pak" type="data_package" lang="sv" />
-    <output filename="electron_strings_sw.pak" type="data_package" lang="sw" />
-    <output filename="electron_strings_ta.pak" type="data_package" lang="ta" />
-    <output filename="electron_strings_te.pak" type="data_package" lang="te" />
-    <output filename="electron_strings_th.pak" type="data_package" lang="th" />
-    <output filename="electron_strings_tr.pak" type="data_package" lang="tr" />
-    <output filename="electron_strings_uk.pak" type="data_package" lang="uk" />
-    <output filename="electron_strings_ur.pak" type="data_package" lang="ur" />
-    <output filename="electron_strings_uz.pak" type="data_package" lang="uz" />
-    <output filename="electron_strings_vi.pak" type="data_package" lang="vi" />
-    <output filename="electron_strings_zh-CN.pak" type="data_package" lang="zh-CN" />
-    <output filename="electron_strings_zh-HK.pak" type="data_package" lang="zh-HK" />
-    <output filename="electron_strings_zh-TW.pak" type="data_package" lang="zh-TW" />
-    <output filename="electron_strings_zu.pak" type="data_package" lang="zu" />
-    <!-- CARO TODO: Pseudolocales? -->
-    <output filename="electron_strings_ar-XB.pak" type="data_package" lang="ar-XB" />
-    <output filename="electron_strings_en-XA.pak" type="data_package" lang="en-XA" />
   </outputs>
-  <translations>
-    <file path="translations/electron_strings_af.xtb" lang="af" />
-    <file path="translations/electron_strings_am.xtb" lang="am" />
-    <file path="translations/electron_strings_ar.xtb" lang="ar" />
-    <file path="translations/electron_strings_as.xtb" lang="as" />
-    <file path="translations/electron_strings_az.xtb" lang="az" />
-    <file path="translations/electron_strings_be.xtb" lang="be" />
-    <file path="translations/electron_strings_bg.xtb" lang="bg" />
-    <file path="translations/electron_strings_bn.xtb" lang="bn" />
-    <file path="translations/electron_strings_bs.xtb" lang="bs" />
-    <file path="translations/electron_strings_ca.xtb" lang="ca" />
-    <file path="translations/electron_strings_cs.xtb" lang="cs" />
-    <file path="translations/electron_strings_cy.xtb" lang="cy" />
-    <file path="translations/electron_strings_da.xtb" lang="da" />
-    <file path="translations/electron_strings_de.xtb" lang="de" />
-    <file path="translations/electron_strings_el.xtb" lang="el" />
-    <file path="translations/electron_strings_en-GB.xtb" lang="en-GB" />
-    <file path="translations/electron_strings_es-419.xtb" lang="es-419" />
-    <file path="translations/electron_strings_es.xtb" lang="es" />
-    <file path="translations/electron_strings_et.xtb" lang="et" />
-    <file path="translations/electron_strings_eu.xtb" lang="eu" />
-    <file path="translations/electron_strings_fa.xtb" lang="fa" />
-    <file path="translations/electron_strings_fi.xtb" lang="fi" />
-    <file path="translations/electron_strings_fil.xtb" lang="fil" />
-    <file path="translations/electron_strings_fr-CA.xtb" lang="fr-CA" />
-    <file path="translations/electron_strings_fr.xtb" lang="fr" />
-    <file path="translations/electron_strings_gl.xtb" lang="gl" />
-    <file path="translations/electron_strings_gu.xtb" lang="gu" />
-    <file path="translations/electron_strings_hi.xtb" lang="hi" />
-    <file path="translations/electron_strings_hr.xtb" lang="hr" />
-    <file path="translations/electron_strings_hu.xtb" lang="hu" />
-    <file path="translations/electron_strings_hy.xtb" lang="hy" />
-    <file path="translations/electron_strings_id.xtb" lang="id" />
-    <file path="translations/electron_strings_is.xtb" lang="is" />
-    <file path="translations/electron_strings_it.xtb" lang="it" />
-    <!-- The translation console uses 'iw' for Hebrew, but we use 'he'. -->
-    <file path="translations/electron_strings_iw.xtb" lang="he" />
-    <file path="translations/electron_strings_ja.xtb" lang="ja" />
-    <file path="translations/electron_strings_ka.xtb" lang="ka" />
-    <file path="translations/electron_strings_kk.xtb" lang="kk" />
-    <file path="translations/electron_strings_km.xtb" lang="km" />
-    <file path="translations/electron_strings_kn.xtb" lang="kn" />
-    <file path="translations/electron_strings_ko.xtb" lang="ko" />
-    <file path="translations/electron_strings_ky.xtb" lang="ky" />
-    <file path="translations/electron_strings_lo.xtb" lang="lo" />
-    <file path="translations/electron_strings_lt.xtb" lang="lt" />
-    <file path="translations/electron_strings_lv.xtb" lang="lv" />
-    <file path="translations/electron_strings_mk.xtb" lang="mk" />
-    <file path="translations/electron_strings_ml.xtb" lang="ml" />
-    <file path="translations/electron_strings_mn.xtb" lang="mn" />
-    <file path="translations/electron_strings_mr.xtb" lang="mr" />
-    <file path="translations/electron_strings_ms.xtb" lang="ms" />
-    <file path="translations/electron_strings_my.xtb" lang="my" />
-    <file path="translations/electron_strings_ne.xtb" lang="ne" />
-    <file path="translations/electron_strings_nl.xtb" lang="nl" />
-    <file path="translations/electron_strings_no.xtb" lang="no" />
-    <file path="translations/electron_strings_or.xtb" lang="or" />
-    <file path="translations/electron_strings_pa.xtb" lang="pa" />
-    <file path="translations/electron_strings_pl.xtb" lang="pl" />
-    <file path="translations/electron_strings_pt-BR.xtb" lang="pt-BR" />
-    <file path="translations/electron_strings_pt-PT.xtb" lang="pt-PT" />
-    <file path="translations/electron_strings_ro.xtb" lang="ro" />
-    <file path="translations/electron_strings_ru.xtb" lang="ru" />
-    <file path="translations/electron_strings_si.xtb" lang="si" />
-    <file path="translations/electron_strings_sk.xtb" lang="sk" />
-    <file path="translations/electron_strings_sl.xtb" lang="sl" />
-    <file path="translations/electron_strings_sq.xtb" lang="sq" />
-    <file path="translations/electron_strings_sr-Latn.xtb" lang="sr-Latn" />
-    <file path="translations/electron_strings_sr.xtb" lang="sr" />
-    <file path="translations/electron_strings_sv.xtb" lang="sv" />
-    <file path="translations/electron_strings_sw.xtb" lang="sw" />
-    <file path="translations/electron_strings_ta.xtb" lang="ta" />
-    <file path="translations/electron_strings_te.xtb" lang="te" />
-    <file path="translations/electron_strings_th.xtb" lang="th" />
-    <file path="translations/electron_strings_tr.xtb" lang="tr" />
-    <file path="translations/electron_strings_uk.xtb" lang="uk" />
-    <file path="translations/electron_strings_ur.xtb" lang="ur" />
-    <file path="translations/electron_strings_uz.xtb" lang="uz" />
-    <file path="translations/electron_strings_vi.xtb" lang="vi" />
-    <file path="translations/electron_strings_zh-CN.xtb" lang="zh-CN" />
-    <file path="translations/electron_strings_zh-HK.xtb" lang="zh-HK" />
-    <file path="translations/electron_strings_zh-TW.xtb" lang="zh-TW" />
-    <file path="translations/electron_strings_zu.xtb" lang="zu" />
-  </translations>
-  <release seq="1">
-    <messages fallback_to_english="true">
-      <message name="IDS_MAC_NOTIFICATION_INLINE_REPLY_BUTTON" desc="Label for the inline reply button inside a macOS notification.">
-        Reply
-      </message>
-      <message name="IDS_MAC_NOTIFICATION_SHOW_BUTTON" desc="Label for the default action button inside a macOS notification.">
-        Show
-      </message>
-    </messages>
+  <release seq="1" allow_pseudo="false">
     <includes>
       <include name="IDR_CONTENT_SHELL_DEVTOOLS_DISCOVERY_PAGE" file="${target_gen_dir}/shell_devtools_discovery_page.html" use_base_dir="false" type="BINDATA" />
     </includes>
   </release>
-</grit>
+</grit>

build/fuses/fuses.json5

@@ -9,5 +9,6 @@
   "embedded_asar_integrity_validation": "0",
   "only_load_app_from_asar": "0",
   "load_browser_process_specific_v8_snapshot": "0",
-  "grant_file_protocol_extra_privileges": "1"
+  "grant_file_protocol_extra_privileges": "1",
+  "wasm_trap_handlers": "1"
 }

build/siso/backend.star

@@ -1,21 +0,0 @@
-# -*- bazel-starlark -*-
-
-load("@builtin//struct.star", "module")
-
-def __platform_properties(ctx):
-    container_image = "docker://gcr.io/chops-public-images-prod/rbe/siso-chromium/linux@sha256:d7cb1ab14a0f20aa669c23f22c15a9dead761dcac19f43985bf9dd5f41fbef3a"
-    return {
-        "default": {
-            "OSFamily": "Linux",
-            "container-image": container_image,
-        },
-        "large": {
-            "OSFamily": "Linux",
-            "container-image": container_image,
-        },
-    }
-
-backend = module(
-    "backend",
-    platform_properties = __platform_properties,
-)

build/siso/main.star

@@ -1,66 +0,0 @@
-load("@builtin//encoding.star", "json")
-load("@builtin//path.star", "path")
-load("@builtin//runtime.star", "runtime")
-load("@builtin//struct.star", "module")
-load("@config//main.star", upstream_init = "init")
-load("@config//win_sdk.star", "win_sdk")
-load("@config//gn_logs.star", "gn_logs")
-
-def init(ctx):
-    mod = upstream_init(ctx)
-    step_config = json.decode(mod.step_config)
-
-    # Buildbarn doesn't support input_root_absolute_path so disable that
-    for rule in step_config["rules"]:    
-      input_root_absolute_path = rule.get("input_root_absolute_path", False)
-      if input_root_absolute_path:
-        rule.pop("input_root_absolute_path", None)
-
-    # Only wrap clang rules with a remote wrapper if not on Linux. These are currently only
-    # needed for X-Compile builds, which run on Windows and Mac.
-    if runtime.os != "linux":
-      for rule in step_config["rules"]:
-        if rule["name"].startswith("clang/") or rule["name"].startswith("clang-cl/"):
-          rule["remote_wrapper"] = "../../buildtools/reclient_cfgs/chromium-browser-clang/clang_remote_wrapper"
-          if "inputs" not in rule:
-            rule["inputs"] = []
-          rule["inputs"].append("buildtools/reclient_cfgs/chromium-browser-clang/clang_remote_wrapper")
-          rule["inputs"].append("third_party/llvm-build/Release+Asserts_linux/bin/clang")
-
-      if "executables" not in step_config:
-        step_config["executables"] = []
-      step_config["executables"].append("buildtools/reclient_cfgs/chromium-browser-clang/clang_remote_wrapper")
-      step_config["executables"].append("third_party/llvm-build/Release+Asserts_linux/bin/clang")
-
-    if runtime.os == "darwin":
-      # Update platforms to match our default siso config instead of reclient configs.
-      step_config["platforms"].update({
-          "clang": step_config["platforms"]["default"],
-          "clang_large": step_config["platforms"]["default"],          
-      })      
-
-    if runtime.os == "windows":
-      # Add additional Windows SDK headers needed by Electron      
-      win_toolchain_dir = win_sdk.toolchain_dir(ctx)
-      if win_toolchain_dir:
-        sdk_version = gn_logs.read(ctx).get("windows_sdk_version")
-        step_config["input_deps"][win_toolchain_dir + ":headers"].extend([
-          # third_party/electron_node/deps/uv/include/uv/win.h includes mswsock.h
-          path.join(win_toolchain_dir, "Windows Kits/10/Include", sdk_version, "um/mswsock.h"),
-          # third_party/electron_node/src/debug_utils.cc includes lm.h
-          path.join(win_toolchain_dir, "Windows Kits/10/Include", sdk_version, "um/Lm.h"),          
-        ])
-      
-      # Update platforms to match our default siso config instead of reclient configs.
-      step_config["platforms"].update({
-          "clang-cl": step_config["platforms"]["default"],
-          "clang-cl_large": step_config["platforms"]["default"],
-          "lld-link": step_config["platforms"]["default"],
-      })
-
-    return module(
-      "config",
-      step_config = json.encode(step_config),
-      filegroups = mod.filegroups,
-      handlers = mod.handlers,
-    )

build/translations/electron_strings_af.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="af">
-  <translation id="2727175239389218057">Antwoord</translation>
-  <translation id="5300589172476337783">Wys</translation>
-</translationbundle>

build/translations/electron_strings_am.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="am">
-  <translation id="2727175239389218057">ምላሽ ስጥ</translation>
-  <translation id="5300589172476337783">አሳይ</translation>
-</translationbundle>

build/translations/electron_strings_ar.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="ar">
-  <translation id="2727175239389218057">الرّد</translation>
-  <translation id="5300589172476337783">عرض</translation>
-</translationbundle>

build/translations/electron_strings_as.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="as">
-  <translation id="2727175239389218057">প্ৰত্যুত্তৰ দিয়ক</translation>
-  <translation id="5300589172476337783">দেখুৱাওক</translation>
-</translationbundle>

build/translations/electron_strings_az.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="az">
-  <translation id="2727175239389218057">Cavablayın</translation>
-  <translation id="5300589172476337783">Göstərin</translation>
-</translationbundle>

build/translations/electron_strings_be.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="be">
-  <translation id="2727175239389218057">Адказаць</translation>
-  <translation id="5300589172476337783">Паказаць</translation>
-</translationbundle>

build/translations/electron_strings_bg.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="bg">
-  <translation id="2727175239389218057">Отговор</translation>
-  <translation id="5300589172476337783">Показване</translation>
-</translationbundle>

build/translations/electron_strings_bn.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="bn">
-  <translation id="2727175239389218057">উত্তর দিন</translation>
-  <translation id="5300589172476337783">দেখান</translation>
-</translationbundle>

build/translations/electron_strings_bs.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="bs">
-  <translation id="2727175239389218057">Odgovori</translation>
-  <translation id="5300589172476337783">Prikaži</translation>
-</translationbundle>

build/translations/electron_strings_ca.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="ca">
-  <translation id="2727175239389218057">Respon</translation>
-  <translation id="5300589172476337783">Mostra</translation>
-</translationbundle>

build/translations/electron_strings_cs.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="cs">
-  <translation id="2727175239389218057">Odpovědět</translation>
-  <translation id="5300589172476337783">Zobrazit</translation>
-</translationbundle>

build/translations/electron_strings_cy.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="cy">
-  <translation id="2727175239389218057">Ateb</translation>
-  <translation id="5300589172476337783">Arddangos</translation>
-</translationbundle>

build/translations/electron_strings_da.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="da">
-  <translation id="2727175239389218057">Svar</translation>
-  <translation id="5300589172476337783">Vis</translation>
-</translationbundle>

build/translations/electron_strings_de.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="de">
-  <translation id="2727175239389218057">Antworten</translation>
-  <translation id="5300589172476337783">Anzeigen</translation>
-</translationbundle>

build/translations/electron_strings_el.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="el">
-  <translation id="2727175239389218057">Απάντηση</translation>
-  <translation id="5300589172476337783">Εμφάνιση</translation>
-</translationbundle>

build/translations/electron_strings_en-GB.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="en-GB">
-  <translation id="2727175239389218057">Reply</translation>
-  <translation id="5300589172476337783">Show</translation>
-</translationbundle>

build/translations/electron_strings_es-419.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="es-419">
-  <translation id="2727175239389218057">Responder</translation>
-  <translation id="5300589172476337783">Mostrar</translation>
-</translationbundle>

build/translations/electron_strings_es.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="es">
-  <translation id="2727175239389218057">Responder</translation>
-  <translation id="5300589172476337783">Mostrar</translation>
-</translationbundle>

build/translations/electron_strings_et.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="et">
-  <translation id="2727175239389218057">Vasta</translation>
-  <translation id="5300589172476337783">Kuva</translation>
-</translationbundle>

build/translations/electron_strings_eu.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="eu">
-  <translation id="2727175239389218057">Erantzun</translation>
-  <translation id="5300589172476337783">Erakutsi</translation>
-</translationbundle>

build/translations/electron_strings_fa.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="fa">
-  <translation id="2727175239389218057">پاسخ دادن</translation>
-  <translation id="5300589172476337783">نمایش</translation>
-</translationbundle>

build/translations/electron_strings_fi.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="fi">
-  <translation id="2727175239389218057">Vastaa</translation>
-  <translation id="5300589172476337783">Näytä</translation>
-</translationbundle>

build/translations/electron_strings_fil.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="fil">
-  <translation id="2727175239389218057">Sumagot</translation>
-  <translation id="5300589172476337783">Ipakita</translation>
-</translationbundle>

build/translations/electron_strings_fr-CA.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="fr-CA">
-  <translation id="2727175239389218057">Répondre</translation>
-  <translation id="5300589172476337783">Afficher</translation>
-</translationbundle>

build/translations/electron_strings_fr.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="fr">
-  <translation id="2727175239389218057">Répondre</translation>
-  <translation id="5300589172476337783">Afficher</translation>
-</translationbundle>

build/translations/electron_strings_gl.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="gl">
-  <translation id="2727175239389218057">Responder</translation>
-  <translation id="5300589172476337783">Mostrar</translation>
-</translationbundle>

build/translations/electron_strings_gu.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="gu">
-  <translation id="2727175239389218057">જવાબ આપો</translation>
-  <translation id="5300589172476337783">બતાવો</translation>
-</translationbundle>

build/translations/electron_strings_hi.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="hi">
-  <translation id="2727175239389218057">जवाब दें</translation>
-  <translation id="5300589172476337783">दिखाएं</translation>
-</translationbundle>

build/translations/electron_strings_hr.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="hr">
-  <translation id="2727175239389218057">Odgovori</translation>
-  <translation id="5300589172476337783">Prikaži</translation>
-</translationbundle>

build/translations/electron_strings_hu.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="hu">
-  <translation id="2727175239389218057">Válasz</translation>
-  <translation id="5300589172476337783">Megjelenítés</translation>
-</translationbundle>

build/translations/electron_strings_hy.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="hy">
-  <translation id="2727175239389218057">Պատասխանել</translation>
-  <translation id="5300589172476337783">Ցույց տալ</translation>
-</translationbundle>

build/translations/electron_strings_id.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="id">
-  <translation id="2727175239389218057">Balas</translation>
-  <translation id="5300589172476337783">Tampilkan</translation>
-</translationbundle>

build/translations/electron_strings_is.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="is">
-  <translation id="2727175239389218057">Svara</translation>
-  <translation id="5300589172476337783">Sýna</translation>
-</translationbundle>

build/translations/electron_strings_it.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="it">
-  <translation id="2727175239389218057">Rispondi</translation>
-  <translation id="5300589172476337783">Mostra</translation>
-</translationbundle>

build/translations/electron_strings_iw.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="iw">
-  <translation id="2727175239389218057">מענה</translation>
-  <translation id="5300589172476337783">הצגה</translation>
-</translationbundle>

build/translations/electron_strings_ja.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="ja">
-  <translation id="2727175239389218057">返信</translation>
-  <translation id="5300589172476337783">表示</translation>
-</translationbundle>

build/translations/electron_strings_ka.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="ka">
-  <translation id="2727175239389218057">პასუხი</translation>
-  <translation id="5300589172476337783">ჩვენება</translation>
-</translationbundle>

build/translations/electron_strings_kk.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="kk">
-  <translation id="2727175239389218057">Жауап беру</translation>
-  <translation id="5300589172476337783">Көрсету</translation>
-</translationbundle>

build/translations/electron_strings_km.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="km">
-  <translation id="2727175239389218057">ឆ្លើយតប</translation>
-  <translation id="5300589172476337783">បង្ហាញ</translation>
-</translationbundle>

build/translations/electron_strings_kn.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="kn">
-  <translation id="2727175239389218057">ಪ್ರತ್ಯುತ್ತರಿಸಿ</translation>
-  <translation id="5300589172476337783">ತೋರಿಸಿ</translation>
-</translationbundle>

build/translations/electron_strings_ko.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="ko">
-  <translation id="2727175239389218057">답장</translation>
-  <translation id="5300589172476337783">표시</translation>
-</translationbundle>

build/translations/electron_strings_ky.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="ky">
-  <translation id="2727175239389218057">Жооп берүү</translation>
-  <translation id="5300589172476337783">Көрсөтүү</translation>
-</translationbundle>

build/translations/electron_strings_lo.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="lo">
-  <translation id="2727175239389218057">ຕອບກັບ</translation>
-  <translation id="5300589172476337783">ສະ​ແດງ​</translation>
-</translationbundle>

build/translations/electron_strings_lt.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="lt">
-  <translation id="2727175239389218057">Atsakyti</translation>
-  <translation id="5300589172476337783">Rodyti</translation>
-</translationbundle>

build/translations/electron_strings_lv.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="lv">
-  <translation id="2727175239389218057">Atbildēt</translation>
-  <translation id="5300589172476337783">Rādīt</translation>
-</translationbundle>

build/translations/electron_strings_mk.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="mk">
-  <translation id="2727175239389218057">Одговори</translation>
-  <translation id="5300589172476337783">Прикажи</translation>
-</translationbundle>

build/translations/electron_strings_ml.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="ml">
-  <translation id="2727175239389218057">മറുപടി നൽകുക</translation>
-  <translation id="5300589172476337783">കാണിക്കുക</translation>
-</translationbundle>

build/translations/electron_strings_mn.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="mn">
-  <translation id="2727175239389218057">Хариулах</translation>
-  <translation id="5300589172476337783">Харуулах</translation>
-</translationbundle>

build/translations/electron_strings_mr.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="mr">
-  <translation id="2727175239389218057">उत्तर द्या</translation>
-  <translation id="5300589172476337783">दर्शवा</translation>
-</translationbundle>

build/translations/electron_strings_ms.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="ms">
-  <translation id="2727175239389218057">Balas</translation>
-  <translation id="5300589172476337783">Paparkan</translation>
-</translationbundle>

build/translations/electron_strings_my.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="my">
-  <translation id="2727175239389218057">စာပြန်ရန်</translation>
-  <translation id="5300589172476337783">ပြရန်</translation>
-</translationbundle>

build/translations/electron_strings_ne.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="ne">
-  <translation id="2727175239389218057">जवाफ दिनुहोस्</translation>
-  <translation id="5300589172476337783">देखाउनुहोस्</translation>
-</translationbundle>

build/translations/electron_strings_nl.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="nl">
-  <translation id="2727175239389218057">Reageren</translation>
-  <translation id="5300589172476337783">Tonen</translation>
-</translationbundle>

build/translations/electron_strings_no.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="no">
-  <translation id="2727175239389218057">Svar</translation>
-  <translation id="5300589172476337783">Vis</translation>
-</translationbundle>

build/translations/electron_strings_or.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="or">
-  <translation id="2727175239389218057">ପ୍ରତ୍ୟୁତ୍ତର ଦିଅନ୍ତୁ</translation>
-  <translation id="5300589172476337783">ପ୍ରଦର୍ଶନ କରନ୍ତୁ</translation>
-</translationbundle>

build/translations/electron_strings_pa.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="pa">
-  <translation id="2727175239389218057">ਜਵਾਬ ਦਿਓ</translation>
-  <translation id="5300589172476337783">ਦਿਖਾਓ</translation>
-</translationbundle>

build/translations/electron_strings_pl.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="pl">
-  <translation id="2727175239389218057">Odpowiedz</translation>
-  <translation id="5300589172476337783">Pokaż</translation>
-</translationbundle>

build/translations/electron_strings_pt-BR.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="pt-BR">
-  <translation id="2727175239389218057">Responder</translation>
-  <translation id="5300589172476337783">Mostrar</translation>
-</translationbundle>

build/translations/electron_strings_pt-PT.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="pt-PT">
-  <translation id="2727175239389218057">Responder</translation>
-  <translation id="5300589172476337783">Mostrar</translation>
-</translationbundle>

build/translations/electron_strings_ro.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="ro">
-  <translation id="2727175239389218057">Răspunde</translation>
-  <translation id="5300589172476337783">Afișează</translation>
-</translationbundle>

build/translations/electron_strings_ru.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="ru">
-  <translation id="2727175239389218057">Ответить</translation>
-  <translation id="5300589172476337783">Показать</translation>
-</translationbundle>

build/translations/electron_strings_si.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="si">
-  <translation id="2727175239389218057">පිළිතුරු දෙන්න</translation>
-  <translation id="5300589172476337783">පෙන්වන්න</translation>
-</translationbundle>

build/translations/electron_strings_sk.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="sk">
-  <translation id="2727175239389218057">Odpovedať</translation>
-  <translation id="5300589172476337783">Zobraziť</translation>
-</translationbundle>

build/translations/electron_strings_sl.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="sl">
-  <translation id="2727175239389218057">Odgovori</translation>
-  <translation id="5300589172476337783">Pokaži</translation>
-</translationbundle>

build/translations/electron_strings_sq.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="sq">
-  <translation id="2727175239389218057">Përgjigju</translation>
-  <translation id="5300589172476337783">Shfaq</translation>
-</translationbundle>

build/translations/electron_strings_sr-Latn.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="sr-Latn">
-  <translation id="2727175239389218057">Odgovori</translation>
-  <translation id="5300589172476337783">Prikaži</translation>
-</translationbundle>

build/translations/electron_strings_sr.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="sr">
-  <translation id="2727175239389218057">Одговори</translation>
-  <translation id="5300589172476337783">Прикажи</translation>
-</translationbundle>

build/translations/electron_strings_sv.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="sv">
-  <translation id="2727175239389218057">Svara</translation>
-  <translation id="5300589172476337783">Visa</translation>
-</translationbundle>

build/translations/electron_strings_sw.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="sw">
-  <translation id="2727175239389218057">Jibu</translation>
-  <translation id="5300589172476337783">Onyesha</translation>
-</translationbundle>

build/translations/electron_strings_ta.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="ta">
-  <translation id="2727175239389218057">பதிலளி</translation>
-  <translation id="5300589172476337783">காண்பி</translation>
-</translationbundle>

build/translations/electron_strings_te.xtb

@@ -1,6 +0,0 @@
-<?xml version="1.0" ?>
-<!DOCTYPE translationbundle>
-<translationbundle lang="te">
-  <translation id="2727175239389218057">రిప్లయి ఇవ్వండి</translation>
-  <translation id="5300589172476337783">చూపించు</translation>
-</translationbundle>