Skip to content

ci: add Dependabot to patch the bundled Electron/Chromium runtime - #79

Closed
BernardJen wants to merge 1 commit into
mainfrom
security/LABS-832-dependabot
Closed

ci: add Dependabot to patch the bundled Electron/Chromium runtime#79
BernardJen wants to merge 1 commit into
mainfrom
security/LABS-832-dependabot

Conversation

@BernardJen

Copy link
Copy Markdown
Contributor

What

Add .github/dependabot.yml with two update ecosystems:

  • npm in /input_viewer_electron — weekly, so the electron pin (currently 42.3.3) and the rest of the toolchain move with upstream releases. Electron packages are grouped so a runtime bump lands as one coherent PR.
  • github-actions in / — keeps the CI/release workflow actions current.

Why — LABS-832

Input Viewer is an Electron app, so input_viewer_electron ships a full Chromium runtime inside the app on the videowall PC. That host is patched by win_updates + winget upgrade --all (labs-windows-mgmt), but neither can see a runtime bundled inside an app — so Chromium security fixes reach the videowall only when Input Viewer is rebuilt with a newer Electron, and nothing currently prompts that rebuild.

This closes that blind spot: Dependabot is now what raises the Electron bump that triggers a rebuild/redeploy.

Not tied to a specific CVE — this is about the missing patch route, found during the LABS-660 Chromium exposure review. Practical risk is lower than a kiosk browser (the app renders local content, not arbitrary web pages), so this is hygiene, not an urgent exposure.

Ref: LABS-832

🤖 Generated with Claude Code

Input Viewer is an Electron app: input_viewer_electron pins electron
42.3.3, i.e. a full Chromium runtime shipped inside the app on the
videowall PC. That host is patched by win_updates + `winget upgrade`
(labs-windows-mgmt), neither of which can see a runtime bundled inside
this app — so Chromium security fixes only reach the videowall when
Input Viewer is rebuilt with a newer Electron, and nothing currently
prompts that rebuild.

Add .github/dependabot.yml so the electron pin (and the rest of the
toolchain) moves with upstream releases, plus github-actions hygiene.
The electron packages are grouped so runtime bumps land as coherent PRs.

Ref: LABS-832

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@BernardJen

Copy link
Copy Markdown
Contributor Author

Superseded: .github/dependabot.yml already landed on main via another route, covering both the npm (/input_viewer_electron) and github-actions ecosystems on a weekly schedule — plus a cooldown this PR lacks. That existing config is what opened #64-#78, including the Electron 42 -> 43 Chromium bump (#77) that LABS-832 asked for, so the goal is met.

Not carried over: the LABS-832 rationale comment and the electron/build-tooling PR grouping. Worth a small follow-up on main if the grouping is wanted.

@BernardJen BernardJen closed this Aug 3, 2026
@BernardJen
BernardJen deleted the security/LABS-832-dependabot branch August 3, 2026 13:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant