// Use when updating the Electron version in the RStudio repository, e.g. bumping to a new release
How to run RStudio Playwright tests in Desktop and Server modes. Use this skill whenever the user asks to run, execute, or launch Playwright tests against RStudio - whether on Desktop (local) or Server (remote). Also use when the user asks about the test command, environment variables, or how to point tests at a server URL. Trigger on phrases like "run the test", "execute on server", "run it on desktop", "run against <IP>", or any request involving npx playwright test for the RStudio test suite.
Patterns and gotchas for authoring RStudio Playwright tests in TypeScript. Use when writing, reviewing, or migrating tests under e2e/rstudio/.
Migrate Python Selenium/Selene electron tests to TypeScript/Playwright. Use when converting tests from rstudio-ide-automation/rstudio_server_pro/electron-tests/ to rstudio/e2e/rstudio/tests/.
Use when updating the Quarto version in the RStudio repository, e.g. bumping to a new release. This skill is for macOS and Linux only.
Use when updating the copilot-language-server version in the RStudio repository, e.g. bumping to a new release. This skill is for macOS and Linux only.
Use when updating Node.js versions in the RStudio repository, e.g. bumping to a new release. Handles both build-time Node (RSTUDIO_NODE_VERSION, used for building Electron/GWT) and installed Node (RSTUDIO_INSTALLED_NODE_VERSION, shipped with the product). This skill is for macOS and Linux only.
| name | rstudio-update-electron |
| description | Use when updating the Electron version in the RStudio repository, e.g. bumping to a new release |
Updates the pinned Electron version across the RStudio codebase and verifies the result.
The user provides the target Electron version (e.g. 39.8.4).
Before doing anything else, confirm the current branch is main. Starting off anything other than main would base the work on the wrong commit.
git branch --show-current
If the output is not main, stop immediately and warn the user that they must switch to main (and pull the latest) before re-running this skill. Do not proceed with any further steps.
NEWS.mdFind the ### Dependencies section and update the Electron version line:
- Electron <NEW_VERSION>
src/node/desktop/package.json and lockfileRun from src/node/desktop:
cd src/node/desktop && npm install --save-dev --save-exact electron@<NEW_VERSION>
The --save-exact flag is required — Electron must be pinned to an exact version (e.g. "electron": "39.8.5", not "^39.8.5"). This prevents uncontrolled upgrades across major/minor versions.
This updates both package.json and package-lock.json in one step. Confirm the command exits successfully (exit code 0). If it fails, report the error and stop.
After the install, verify that:
package.json has the exact version with no ^ or ~ prefix.package-lock.json contains the new Electron version.The lockfile must be included in the commit — if it drifts from the manifest, npm ci in CI will fail.
Run from src/node/desktop:
cd src/node/desktop && npm test
Confirm the command exits successfully. If tests fail, report the failures and stop.
Report that the Electron version has been updated and both npm i and npm test passed.