electron-chromium-upgrade

Guide Chromium version upgrades in Electron using e sync --3 and patch conflict resolution.

122k|17.4k|Updated Apr 12, 2013
One-click install
npx skills add https://github.com/electron/electron --skill electron-chromium-upgrade
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: electron-chromium-upgrade
Source: https://github.com/electron/electron/tree/main/.claude/skills/electron-chromium-upgrade
Command: npx skills add https://github.com/electron/electron --skill electron-chromium-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill guides engineers through Chromium version upgrades in the Electron project, ensuring patch conflicts are resolved efficiently and upgrades proceed without breaking builds.

Core Features & Use Cases

  • Structured upgrade workflow: from patch application to post-upgrade verification using e sync --3, conflict resolution, and exporting patches.
  • Policy-driven commits: follow phase-one guidelines to commit patch fixes with clear references.
  • Contextual guidance: applicable on roller/chromium/main to resolve patch conflicts and maintain patch integrity.

Quick Start

Run e sync --3 on the roller/chromium/main branch to start applying Chromium patches, resolve conflicts as they arise, then run e patches all and commit following the phase-one commit guidelines.

Frequently Asked Questions about electron-chromium-upgrade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upgrade Chromium in Electron and resolve patch conflicts?

To upgrade Chromium in Electron, run e sync --3 on the roller/chromium/main branch to apply patches via three-way application, resolve conflicts as they arise, then export using e patches all and commit following phase-one guidelines.

What is the three-way patch application process for Electron Chromium upgrades?

The three-way patch application process during an Electron Chromium upgrade uses e sync --3 to apply patches on the roller/chromium/main branch, detecting and managing conflicts efficiently so the build proceeds without breaking.

How do I export patches after a Chromium version upgrade in Electron?

After resolving patch conflicts during the Chromium upgrade, run e patches all to export patches, then commit the patch fixes by adhering to phase-one commit guidelines with clear references.

Do I need a specific branch to handle Electron Chromium patch conflicts?

Yes, this structured upgrade workflow applies when working on the roller/chromium/main branch to upgrade Electron's Chromium dependency, handle patch conflicts, and prepare subsequent patch exports.

Why do my Electron builds break after applying Chromium patches?

Builds break when patch conflicts arise during Chromium version upgrades; resolving these conflicts efficiently on the roller/chromium/main branch using e sync --3 ensures the upgrade proceeds without breaking builds.

What commit guidelines should I follow when fixing Electron patch conflicts?

When fixing patch conflicts during a Chromium upgrade, follow the phase-one commit guidelines to commit patch fixes with clear references, maintaining patch integrity throughout the process.