Skip to content

build: take @systemfsoftware packages from npm - #47

Merged
systemfsoftware-bot merged 2 commits into
mainfrom
build/packages-from-npm
Nov 15, 2026
Merged

systemfsoftware-bot merged 2 commits into
mainfrom
build/packages-from-npm

Conversation

@systemfsoftware-bot

Copy link
Copy Markdown
Contributor

Every @systemfsoftware package is published to npm through trusted publishing, so packages no longer come from Nix-built tarballs under .deps/.

  • Removes the file:.deps overrides, mkProducerTarballs, the producer-tarballs output and the dev shell's tarball hook. workspace-tarballs stays: the release workflow builds what it publishes with it.
  • Manifests and the stryker catalog name caret ranges on versions npm serves; pnpm-lock.yaml is re-resolved from npm.
  • READMEs and contributor docs install with pnpm add.

Every @systemfsoftware package is published to npm through trusted publishing,
so the file:.deps overrides, mkProducerTarballs and the dev shell's tarball
hook go. Manifests and the stryker catalog name caret ranges on the npm
versions; pnpm-lock.yaml holds the exact resolution. READMEs install with
pnpm add.
@systemfsoftware-bot
systemfsoftware-bot merged commit 4b140be into main Nov 15, 2026
4 checks passed
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