Version Packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@inkandswitch/patchwork@0.2.0

Minor Changes

• 2fffabe: setup() now uses packageListURL as given instead of letting localStorage.systemPackageListURL silently replace it. A site that wants a dev override resolves it itself and passes the result in:

  const packageListURL =
    new URLSearchParams(location.search).get("system-package-list") ||
    localStorage.getItem("systemPackageListURL") ||
    DEFAULT_PACKAGE_LIST;

  This keeps the precedence in one place — the site — so a site can add its own override sources without fighting the library for priority.

Patch Changes

• 5f70c14: Add repository metadata pointing at inkandswitch/patchwork-next, so npm links each package to its source directory and can attest provenance when published from CI.
• Updated dependencies [5f70c14]
  • @inkandswitch/patchwork-bootloader@0.5.1
  • @inkandswitch/patchwork-filesystem@0.2.4
  • @inkandswitch/patchwork-elements@4.0.3
  • @inkandswitch/patchwork-plugins@1.0.2

@inkandswitch/patchwork-e2e@0.2.0

Minor Changes

• 48e292a: Publish the e2e suite as a package with a patchwork-e2e bin, so any Patchwork site repo can run it against its own build. Run it from the repo root after a build; it starts the site's preview server (pnpm preview, overridable with --preview-command and --site-dir) and points the suite at it, writing reports and traces into the directory you ran from.

  The cross-profile sync test against a deployed site now takes its origin from --live-site=<url> (or PATCHWORK_E2E_LIVE_SITE) instead of a hardcoded patchwork.inkandswitch.com, and skips when neither is set. Also new: --base-url to test an already-running server, --port, and --extra-tests-dir to run a site's own specs alongside the suite as a <browser>:extra project — those get the same fixtures, baseURL and preview server, and can import createDoc, waitForRepoReady and friends from @inkandswitch/patchwork-e2e/helpers.

  The preview server now takes the first free port from 5173 up, and runs with --strictPort. Before, vite preview would quietly move to another port when 5173 was busy and the run would hang until Playwright's two-minute webServer timeout expired.

  The suite is compiled to dist/ and published as JavaScript. Playwright does not transform files under node_modules, so shipping the TypeScript sources made the config unloadable for consumers.

@inkandswitch/patchwork-bootloader@0.5.1

Patch Changes

• 5f70c14: Add repository metadata pointing at inkandswitch/patchwork-next, so npm links each package to its source directory and can attest provenance when published from CI.
• Updated dependencies [5f70c14]
  • @inkandswitch/patchwork-filesystem@0.2.4
  • @inkandswitch/patchwork-elements@4.0.3
  • @inkandswitch/patchwork-plugins@1.0.2

@inkandswitch/patchwork-elements@4.0.3

Patch Changes

• 5f70c14: Add repository metadata pointing at inkandswitch/patchwork-next, so npm links each package to its source directory and can attest provenance when published from CI.
• Updated dependencies [5f70c14]
  • @inkandswitch/patchwork-filesystem@0.2.4
  • @inkandswitch/patchwork-plugins@1.0.2

@inkandswitch/patchwork-filesystem@0.2.4

Patch Changes

• 5f70c14: Add repository metadata pointing at inkandswitch/patchwork-next, so npm links each package to its source directory and can attest provenance when published from CI.

@inkandswitch/patchwork-plugins@1.0.2

Patch Changes

• 5f70c14: Add repository metadata pointing at inkandswitch/patchwork-next, so npm links each package to its source directory and can attest provenance when published from CI.
• Updated dependencies [5f70c14]
  • @inkandswitch/patchwork-filesystem@0.2.4

@inkandswitch/edge-handles@0.1.1

Patch Changes

• 5f70c14: Add repository metadata pointing at inkandswitch/patchwork-next, so npm links each package to its source directory and can attest provenance when published from CI.

[netlify]

✅ Deploy Preview for gaiosub ready!

Name	Link
🔨 Latest commit	ee3e441
🔍 Latest deploy log	https://app.netlify.com/projects/gaiosub/deploys/6a5fd635db60fd0008731c4f
😎 Deploy Preview	https://deploy-preview-377--gaiosub.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.