3 Commits

Include renames

Author	SHA1	Message	Date
paseo-bot[bot]and3ae3ae	c6d1822e2b	fix(server): install registry plugins under npm 12 ... npm 12 rejects the reviewed tarball URL by default. Allow remote artifacts only at the staging root while preserving the reviewed version, URL and integrity checks. Read npm pack filenames so the fixture registry supports the npm 12 output shape. Closes #7794 Co-authored-by: 3ae3ae <ogyshjsm@naver.com>	2026-11-02 07:24:18 +00:00
paseo-bot[bot]	8537709e72	test(server): reduce npm fixture setup in the Windows timeout case (#8106) ... * test(server): batch npm fixture packing to reduce Windows setup time * test(server): describe the batched npm fixture setup budget --------- Co-authored-by: paseo-bot[bot] <266920839+paseo-bot[bot]@users.noreply.github.com>	2026-10-28 12:57:33 +00:00
Mohamed Boudra	047f40e623	Install npm plugins and review source updates (#4975) ... * feat(plugins): unify source installation and simplify plugin settings * feat(plugins): install npm sources and review CLI updates Treat install selectors as one-time choices. Keep source identity separate from the installed revision, and resolve ordinary updates from the current upstream default. npm only acquires directories; plugin loading remains independent of npm. * fix(plugins): preserve CLI diagnostics and exercise reviewed updates Move new source capability coverage to real browser journeys. Update the requirements regression to exercise preview and apply, and preserve the existing duplicate-selector diagnostic across positional option scopes. * test(plugins): remove unused pending helper * test(plugins): pack registry fixtures with the Windows command runner * test(plugins): assert failed client contribution setup * docs(plugins): consolidate guides and document npm publishing * docs(plugins): introduce publishing choices before npm instructions * test(plugins): own browser journey cleanup in a fixture * feat(plugins): prepare scaffolded packages for publishing	2026-09-17 10:22:20 +02:00