Add curl installer scripts for standalone CLI distribution by bcotrim · Pull Request #3064 · Automattic/studio

bcotrim · 2026-04-10T17:03:03Z

Related issues

Related to STU-1525

How AI was used in this PR

AI helped draft and iterate on the standalone installer/bundling changes, reason through review feedback, and inspect CI logs. The generated changes were reviewed, adjusted, and verified locally before pushing.

Proposed Changes

This PR makes the Studio CLI available as a standalone terminal install, so users can run studio without first installing or launching the desktop app. This supports headless workflows, CI use, remote development, scripting, and users who only need CLI access.

The installers (install.sh / install.ps1) download a platform tarball, verify its SHA-256 checksum before touching an existing install, extract it, and put studio on the user's PATH. The bundle reuses the same runtime layout the desktop app has shipped for a long time — a real Node.js binary plus the packaged CLI — fronted by a small studio launcher, nvm/rustup-style. This keeps the CLI's runtime behavior (child processes, JSPI, browser installs) identical to the desktop app and dev environment, and leaves both the desktop app's packaging and the CLI's build/runtime code unchanged — the diff is almost entirely the new bundling and installer layer, plus detection so desktop-managed CLI installs don't overwrite standalone ones.

This PR does not publish the public install endpoints yet. Follow-up work still needs to host install.sh / install.ps1 and publish release bundles/checksums to https://wp.build/releases/.

Trade-offs:

studio on PATH is a launcher script rather than a single binary (same pattern as nvm/rustup installs).
Native modules in the bundle are built by the runner that creates it, so each platform's bundle must be built on its own platform in CI.
The standalone CLI downloads the native PHP binary on first native-runtime use instead of bundling it into the installer download.

Testing Instructions

Local standalone bundle smoke test

Build the standalone bundle for the current platform:
```
npm run cli:bundle
```
Confirm standalone-bundles/ contains studio-cli-<platform>-<arch>.tar.gz and its .sha256 checksum.

macOS / Linux installer

Install from the local bundle:

STUDIO_CLI_URL="$PWD/standalone-bundles" bash scripts/standalone/install.sh

Source the updated shell profile or open a new terminal.
Verify the installed CLI:
```
studio --help
studio --version
```
Verify the symlink points to the standalone install:
```
ls -la ~/.local/bin/studio
```

Create and start a site to exercise the daemon and server child processes:

studio site create --path ~/studio-test-site --skip-browser
studio site stop --all

Re-run the installer and confirm it upgrades in place without duplicating the PATH entry.

Windows installer

Build the Windows standalone bundle on a Windows runner:
```
npm run cli:bundle
```

Install from the local bundle:

$env:STUDIO_CLI_URL = "$PWD\standalone-bundles"
# -ExecutionPolicy Bypass is only needed to run the .ps1 file directly;
# the public `irm ... | iex` flow isn't gated by the execution policy.
powershell -ExecutionPolicy Bypass -File scripts\standalone\install.ps1

Open a new terminal and verify:

where.exe studio
studio --help
studio --version

Desktop package integration

Desktop packaging is unchanged from trunk (resources/bin/node + resources/cli/). To sanity check:

Package the desktop app for the current platform:
```
npm -w studio-app run package
```

Run the packaged CLI shim:

apps/studio/out/Studio-<platform>-<arch>/Studio.app/Contents/Resources/bin/studio-cli.sh --version

Adjust the resource path for Linux/Windows package output.

Launch the packaged desktop app and confirm Settings -> Preferences reports the Studio CLI as available without overwriting a standalone install.
Run the relevant E2E suite against the packaged app for both Playground and native-PHP site runtimes.

Notes

The future public install flow will use curl -fsSL https://wp.build/install.sh | bash on macOS/Linux and irm https://wp.build/install.ps1 | iex on Windows after the release publishing follow-up lands.

Pre-merge Checklist

Have you checked for TypeScript, React or other console errors?

…latform support

…ing it

wpmobilebot · 2026-04-13T15:41:34Z

📊 Performance Test Results

Comparing 15b1272 vs trunk

app-size

Metric	trunk	`15b1272`	Diff	Change
App Size (Mac)	2334.12 MB	2334.13 MB	+0.00 MB	⚪ 0.0%

site-editor

Metric	trunk	`15b1272`	Diff	Change
load	1768 ms	1752 ms	16 ms	⚪ 0.0%

site-startup

Metric	trunk	`15b1272`	Diff	Change
siteCreation	8500 ms	8515 ms	+15 ms	⚪ 0.0%
siteStartup	3923 ms	3881 ms	42 ms	⚪ 0.0%

Results are median values from multiple test runs.

Legend: 🟢 Improvement (faster) | 🔴 Regression (slower) | ⚪ No change (<50ms diff)

fredrikekelund · 2026-04-14T10:03:08Z

I already mentioned this on Slack, but for the record: I think we should look in to Node's native "single executable application" feature https://nodejs.org/docs/latest-v25.x/api/single-executable-applications.html.

This would simplify the installer, and ideally, we could reuse this logic for the bundled CLI.

…ibution

…on, SHA-256 output

fredrikekelund

I like the overall approach here and I definitely think we're doing the right thing in aligning the CLI build between the app and the standalone CLI bundle. However, it seems like the "everything in main.mjs" approach I suggested has the caveat of increased baseline memory usage. A 20MB JS script is definitely pushing it in terms of filesize…

On trunk, the process manager daemon occupies ~30MB on my machine. On this branch, it's closer to 100MB. Not necessarily a deal breaker, although TBH, this is probably more of a drawback than reducing the number of separate assets is a benefit. How do you feel about reverting to your previous approach, @bcotrim?

We still need to implement some kind of self-updater in the CLI, and we need to figure out distribution (as you rightly point out, @bcotrim).

fredrikekelund · 2026-06-11T07:24:54Z

+					// Single-file bundle so the SEA can embed one self-contained main.mjs
+					// without a chunk-name scavenger hunt at runtime. Requires a single
+					// entry — ok for prod since there's only `main`.
+					inlineDynamicImports: true,


I'd consider putting this in vite.config.base.ts to ensure we align behavior as closely as possible between all builds. I don't think we need to make an exception for npm, either…

Except I ultimately landed on that we might want to revert this approach and go with what you originally had, @bcotrim 😅

fredrikekelund · 2026-06-11T08:04:03Z

+			rollupOptions: {
+				external: ( id ) => {
+					if ( id.includes( 'blueprint-schema-validator' ) ) {
+						return false;
+					}
+					if ( isNodeBuiltin( id ) ) {
+						return true;
+					}
+					// Externalize every dependency — the end user installs them.
+					return packageJsonDependencies.some(
+						( dep ) => id === dep || id.startsWith( dep + '/' )
+					);
+				},
+			},


Nice 👍 We should have done this before anyway.

fredrikekelund · 2026-06-11T08:51:14Z

Do we even need this and studio-cli.bat now? Maybe that's fodder for a different PR, but it seems like an unnecessary intermediate layer now.

fredrikekelund · 2026-06-11T09:13:07Z

+	// Stream the asset to tar's stdin and extract in-place (cwd = destDir).
+	// No paths in argv => no GNU-tar "Cannot connect to C:" failure.
+	try {
+		execSync( 'tar -xz', {


I see now that we get the assets with the sea.getAsset() API, so I guess the answer here is no.

fredrikekelund · 2026-06-11T09:16:16Z

+{
+	"main": "entry.cjs",
+	"output": "bundle.blob",
+	"disableExperimentalSEAWarning": true,


Suggested change

"disableExperimentalSEAWarning": true,

"disableExperimentalSEAWarning": true,

"execArgv": ["--experimental-wasm-jspi"],

I haven't verified, but per the docs, this should let us work around the JSPI problem.

fredrikekelund · 2026-06-11T09:21:00Z

A 400 MB reduction in installer size is incredibly impressive. That's a lot more than I would have expected. We're not actually shipping less code here, either… Is all of that attributable to the fact that we compress the CLI dependencies?

… scripts

…staller # Conflicts: # .buildkite/commands/run-e2e-tests.sh # apps/cli/lib/pull/migration-client.ts # apps/cli/vite.config.base.ts

…kg/pkg

…staller

… managed

bcotrim · 2026-06-11T21:06:11Z

@fredrikekelund I reverted back to the initial approach. Can you give the PR another review, please?
I didn't include the build optimization in this PR, and will add it in a follow-up to reduce scope.

fredrikekelund

I think this is a pragmatic strategy 👍 Without a fully standalone executable, I agree there's really no good reason to go through the SEA packaging/unpackaging hassle.

I recommend addressing the studio site stop --all thing before landing this PR. Other than that, this tests well on macOS. I'm about to test it on Windows, too. If it works as expected there, I'll approve and let you handle the studio site stop --all thing without waiting for another review from me, @bcotrim

fredrikekelund · 2026-06-15T09:26:39Z

+install_studio() {
+	BUNDLE_NAME="studio-cli-${PLATFORM}-${ARCH}.tar.gz"
+	BUNDLE_URL="${BASE_URL}/${BUNDLE_NAME}"
+
+	mkdir -p "$INSTALL_DIR"
+
+	# Download, verify, and extract in a staging dir on the same filesystem as
+	# the final paths. A failed or corrupt download never touches a previously
+	# working install.
+	STAGING_DIR="$(mktemp -d "${INSTALL_DIR}/.studio-install.XXXXXX")"
+	trap 'rm -rf "$STAGING_DIR"' EXIT
+
+	TMP_BUNDLE="$STAGING_DIR/$BUNDLE_NAME"
+
+	echo "Downloading Studio CLI..."
+	download "$BUNDLE_URL" "$TMP_BUNDLE"
+	download "${BUNDLE_URL}.sha256" "$TMP_BUNDLE.sha256"
+
+	echo "Verifying checksum..."
+	if ! verify_checksum "$TMP_BUNDLE" "$TMP_BUNDLE.sha256"; then
+		echo "Error: checksum verification failed. Aborting; existing install left untouched." >&2
+		exit 1
+	fi
+
+	echo "Installing to $INSTALL_DIR..."
+	mkdir -p "$STAGING_DIR/extracted"
+	tar -xzf "$TMP_BUNDLE" -C "$STAGING_DIR/extracted"
+
+	# Replace only the runtime dirs. Config files in $INSTALL_DIR (shared.json,
+	# cli.json, app.json, …) are left untouched.
+	rm -rf "$INSTALL_DIR/cli" "$INSTALL_DIR/bin"
+	mv "$STAGING_DIR/extracted/cli" "$INSTALL_DIR/cli"
+	mv "$STAGING_DIR/extracted/bin" "$INSTALL_DIR/bin"
+
+	chmod +x "$INSTALL_DIR/bin/node" "$INSTALL_DIR/bin/studio"
+
+	# Symlink to PATH
+	mkdir -p "$BIN_DIR"
+	ln -sf "$INSTALL_DIR/bin/studio" "$BIN_DIR/studio"
+}


This function doesn't account for cases where a standalone Studio CLI is already installed on the system. I suggest something like this: if ~/.studio/bin or ~/.studio/cli already exist, try running studio site stop --all before mv "$STAGING_DIR/extracted/cli" "$INSTALL_DIR/cli"

fredrikekelund · 2026-06-15T09:34:22Z

+
+# --- Install ---
+
+function Install-StudioCli {


Same issue here as in install.sh: we aren't accounting for existing standalone Studio CLI installs.

On Posix, removing the directory will mess up running processes, whereas on Windows, the installer will fail (since the kernel will disallow removing ~/.studio/cli or ~/.studio/bin if any process has a handle on the files in that directory).

fredrikekelund · 2026-06-15T09:41:37Z

+ * NOTE: The `cli:package` step mutates `apps/cli/node_modules`. If you need a
+ * clean tree afterwards, run `npm ci` from the repo root to reset it.


Not a show stopper, but we get around this problem when building the Electron app locally by copying the entire repo to a temporary build dir, running all the build commands there (including npm run cli:package) and then copying back the output.

Might be a nice touch for this script, too

fredrikekelund · 2026-06-15T09:43:17Z

+	run(
+		`npx tsx scripts/download-node-binary.ts ${ platformArg } ${ archArg } "${ path.join(
+			stagingDir,
+			'bin'
+		) }"`
+	);


Fully optional, but we could statically import main() from scripts/download-node-binary.ts instead of running this via npx tsx

fredrikekelund · 2026-06-15T09:53:23Z

We can tackle this in a follow-up PR, but these changes will make it so the Studio CLI for terminal toggle in the app's settings modal is always enabled if the standalone CLI installed. If the user tries to uninstall it, it would silently fail.

I'd argue the ideal behavior would be to disable the UI toggle when the CLI is externally managed.

fredrikekelund

We need -ExecutionPolicy Bypass when running the PowerShell script. Other than that, this tests well on Windows 👍

Please note that even though I'm approving now, I still recommend we address the studio site stop --all thing I raised before landing this PR.

fredrikekelund · 2026-06-15T11:09:05Z

I had to run this script like so to make it work:

powershell -ExecutionPolicy Bypass -File scripts\standalone\install.ps1

…atest alias (#3835) ## Related issues - Related to STU-1780 - Builds on #3064 (standalone bundling + curl installers) and Automattic/wpcom#221531 (adds the `WordPress.com Studio CLI` Apps CDN product) ## How AI was used in this PR AI helped map the existing Apps CDN / Fastlane / Buildkite release flow, design the CLI upload to mirror the established PHP CLI binary path, switch the installers to the CDN `latest` alias, and verify the work locally (Ruby + YAML syntax, the fastlane helper tests, a `studio_cli_cdn_builds`/upload dry-run harness, an end-to-end `install.sh` behavior harness, and a real throwaway upload against the production CDN). All changes were reviewed and validated before pushing. ## Proposed Changes Makes the standalone Studio CLI available to users without the desktop app, kept current automatically. - **Every Studio build now publishes the standalone CLI bundles to the Apps CDN** (under the `WordPress.com Studio CLI` product), for nightly/dev, beta, and stable alike. The bundles track the app build exactly — same version and visibility — so stable bundles become public at publish time just like the app, and there's no separate step to run. - **The curl installers download straight from the CDN's versionless `latest` alias**, so no bespoke redirect service is needed. `STUDIO_CLI_VERSION` pins a specific version, and `STUDIO_CLI_URL` is retained as a bypass for local builds and mirrors. Both paths rely on HTTPS plus a staged-extraction guard (a corrupt download fails at `tar -xzf` before touching an existing install); the bundle's SHA-256 is still recorded as CDN build metadata. - Bundles are published as `studio-cli-<platform>-<arch>.tgz` (gzipped tar) for all six platform/arch targets. Trade-off / remaining dependency: the `install.sh` / `install.ps1` scripts themselves still need public hosting for the `curl … | bash` / `irm … | iex` entry points (the CDN serves uploaded builds, not arbitrary scripts) — a separate WordPress.com-side task. Until that lands, the CLI is installable via the direct CDN URL or `STUDIO_CLI_URL`. ## Testing Instructions **Fastlane (dry run, no remote side effects):** ```sh npm run cli:bundle -- darwin arm64 # build a bundle (repeat per platform/arch) DRY_RUN=true bundle exec fastlane publish_studio_cli_binaries version:"v1.11.0" ``` Confirm it lists the six platform/arch uploads with the right product, platform labels, version, and sha. Existing helper tests still pass: `bash .buildkite/commands/run-fastlane-tests.sh`. **Real CDN upload (verified):** a throwaway `0.0.1` / Internal build was uploaded to the production `WordPress.com Studio CLI` product via the same `media/new` endpoint the lane posts to — confirming the upload path works and that the `.tgz` file type is accepted (see Notes). **Installer — `STUDIO_CLI_URL` bypass:** ```sh STUDIO_CLI_HOME="$(mktemp -d)" STUDIO_CLI_URL="$PWD/standalone-bundles" bash scripts/standalone/install.sh ``` **Installer — default CDN mode:** with bundles published, a fresh install resolves `https://appscdn.wordpress.com/downloads/wordpress-com-studio-cli/<slug>/latest/full-install` (e.g. `mac-silicon`), and `STUDIO_CLI_VERSION=v1.11.0` pins that version. **Windows:** `install.ps1` mirrors the same logic (win32 → `windows-x64` / `windows-arm64`). It was validated structurally but **needs a real Windows run to confirm** (no `pwsh` locally). ## Pre-merge Checklist - [ ] Have you checked for TypeScript, React or other console errors? — N/A (changes are Fastlane/Ruby, Buildkite YAML, PowerShell/shell installers, and docs; no app code). ### Notes for reviewers - **Bundles are `.tgz`, not `.tar.gz`.** The Apps CDN's upload validation (WordPress `wp_check_filetype_and_ext`) rejects the `.tar.gz` *double extension* — even though `gz` is allow-listed — while `.tgz` (same gzip bytes, single extension, already on the CDN's accepted-mime list) uploads cleanly. `tar -xzf` handles both identically, so the installers and extraction logic are unchanged. - **macOS quarantine:** `install.sh` clears `com.apple.quarantine` from the extracted files. The bundled `.node` modules are unsigned, so a *browser-downloaded* bundle would otherwise be Gatekeeper-blocked ("library load disallowed by system policy"). The `curl … | bash` path isn't quarantined, so this is defensive for manual / MDM-managed installs. (Signing + notarizing the macOS bundle is a possible future hardening, tracked separately.) - **Cross-arch bundles are safe within an OS** (so the existing CI matrix runners are fine): the CLI uses no-fsevents chokidar, `fs-ext-extra-prebuilt` ships both arches per-OS, and the target Node binary is downloaded per arch. Only cross-*OS* needs a native runner, which the matrix already provides. - Stable bundles flip to public automatically because their CDN post IDs ride the draft GitHub release through the existing `create_draft_github_release` → `make_cdn_builds_public` path — no change to that logic.

Add curl installer scripts for standalone CLI distribution

4d541de

bcotrim self-assigned this Apr 10, 2026

bcotrim and others added 7 commits April 13, 2026 10:33

Convert create-standalone-bundle from shell to TypeScript for cross-p…

f77f9c4

…latform support

Add cli:bundle npm script for standalone bundle creation

3fab289

Preserve config files during install (don't wipe ~/.studio)

2c988a6

Merge branch 'trunk' into stu-1525-add-curl-installer

bac4423

Use tar.gz for all platforms instead of zip for Windows

d8447c4

Detect standalone CLI on Windows to prevent desktop app from overwrit…

7f43d56

…ing it

Merge branch 'trunk' into stu-1525-add-curl-installer

24fef1b

bcotrim requested review from a team and fredrikekelund April 13, 2026 15:03

bcotrim marked this pull request as ready for review April 13, 2026 15:20

Simplify bundle script and fix Windows installer extraction

da3ff4e

Merge branch 'trunk' into stu-1525-add-curl-installer

6e97c91

bcotrim and others added 14 commits April 14, 2026 17:03

Bundle CLI as a single executable binary for standalone and app distr…

36d8cb6

…ibution

Remove @yao-pkg/pkg and unused CLI launcher script

1c55a5c

Merge branch 'trunk' into stu-1525-add-curl-installer

100c9cd

Fix lint errors in bundle entry point

49a2c89

Clean up packaged bin directory and remove unused node binaries

bfa005e

Fix Windows tar path handling and clean up packaged bin directory

df41f34

Add --force-local to tar commands for Windows compatibility

4b9bdd2

Only use --force-local tar flag on Windows (BSD tar doesn't support it)

878c104

Merge branch 'trunk' into stu-1525-add-curl-installer

e52247c

Externalize trash package to fix site deletion in bundled binary

24fa120

Harden standalone CLI extraction: lockfile, auto-derived bundle-versi…

570bfd6

…on, SHA-256 output

Verify SHA-256 checksum and tighten PATH matching in curl installers

9a20492

Return nullable CLI binary path, handle Windows junction, add paths test

274ebde

Merge branch 'trunk' into stu-1525-add-curl-installer

801c67f

Rely on module.builtinModules

43f08a8

fredrikekelund approved these changes Jun 11, 2026

View reviewed changes

bcotrim added 12 commits June 11, 2026 11:48

Revert CLI bundling from Node SEA binary to bundled node + files

bc7c7fb

Distribute standalone CLI as a tarball with bundled node and launcher…

71a6483

… scripts

Detect standalone CLI on Windows via launcher and bundled node

c3e76d0

Merge remote-tracking branch 'origin/trunk' into stu-1525-add-curl-in…

ffcb203

…staller # Conflicts: # .buildkite/commands/run-e2e-tests.sh # apps/cli/lib/pull/migration-client.ts # apps/cli/vite.config.base.ts

Restore trunk files dropped by trunk merge resolution

e5343e9

Revert single-file CLI build and internal command consolidation

cebb9fc

Drop explicit esbuild dev dependency restored transitively via @yao-p…

09fb44e

…kg/pkg

Merge remote-tracking branch 'origin/trunk' into stu-1525-add-curl-in…

a8a2748

…staller

Drop packaged CLI smoke from e2e script, desktop bundling is unchanged

8f62553

Reclaim broken studio symlinks instead of treating them as externally…

ff98eab

… managed

Parameterize chrome-sandbox removal with ARCH in e2e script

aa03891

Reuse desktop CLI launcher scripts for the standalone bundle

ad285dd

bcotrim requested a review from fredrikekelund June 11, 2026 21:05

bcotrim assigned bcotrim and unassigned bcotrim Jun 12, 2026

fredrikekelund reviewed Jun 15, 2026

View reviewed changes

fredrikekelund approved these changes Jun 15, 2026

View reviewed changes

bcotrim added 2 commits June 15, 2026 12:33

Stop a running standalone CLI before reinstalling over it

f4cc7d4

Import download-node-binary directly in the standalone bundle script

ccc9916

bcotrim requested a review from a team as a code owner June 15, 2026 11:34

bcotrim and others added 2 commits June 15, 2026 14:10

Document PowerShell execution-policy bypass for local install testing

e23ebc1

Merge branch 'trunk' into stu-1525-add-curl-installer

15b1272

bcotrim merged commit 962e523 into trunk Jun 15, 2026
12 checks passed

bcotrim deleted the stu-1525-add-curl-installer branch June 15, 2026 13:57

bcotrim mentioned this pull request Jun 15, 2026

Publish standalone CLI bundles to Apps CDN and install from the CDN latest alias #3835

Merged

1 task

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Add curl installer scripts for standalone CLI distribution - #3064

Add curl installer scripts for standalone CLI distribution#3064
bcotrim merged 81 commits into
trunkfrom
stu-1525-add-curl-installer

bcotrim commented Apr 10, 2026 •

edited

Loading

wpmobilebot commented Apr 13, 2026 •

edited

Loading

fredrikekelund commented Apr 14, 2026

fredrikekelund left a comment

fredrikekelund Jun 11, 2026

fredrikekelund Jun 11, 2026

fredrikekelund Jun 11, 2026

fredrikekelund Jun 11, 2026

fredrikekelund Jun 11, 2026

fredrikekelund Jun 11, 2026

fredrikekelund commented Jun 11, 2026

bcotrim commented Jun 11, 2026

fredrikekelund left a comment

fredrikekelund Jun 15, 2026

fredrikekelund Jun 15, 2026

fredrikekelund Jun 15, 2026

fredrikekelund Jun 15, 2026

fredrikekelund Jun 15, 2026

fredrikekelund left a comment

fredrikekelund Jun 15, 2026

Uh oh!

Labels

3 participants

	"disableExperimentalSEAWarning": true,
	"disableExperimentalSEAWarning": true,
	"execArgv": ["--experimental-wasm-jspi"],

		* NOTE: The `cli:package` step mutates `apps/cli/node_modules`. If you need a
		* clean tree afterwards, run `npm ci` from the repo root to reset it.

Uh oh!

Conversation

bcotrim commented Apr 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Related issues

How AI was used in this PR

Proposed Changes

Testing Instructions

Local standalone bundle smoke test

macOS / Linux installer

Windows installer

Desktop package integration

Notes

Pre-merge Checklist

wpmobilebot commented Apr 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

📊 Performance Test Results

app-size

site-editor

site-startup

fredrikekelund commented Apr 14, 2026

fredrikekelund left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

fredrikekelund commented Jun 11, 2026

bcotrim commented Jun 11, 2026

fredrikekelund left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

fredrikekelund left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Uh oh!

Labels

3 participants

bcotrim commented Apr 10, 2026 •

edited

Loading

wpmobilebot commented Apr 13, 2026 •

edited

Loading