Repository navigation
build: take @systemfsoftware packages from npm - #136
Merged
Merged
Conversation
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 catalogs name caret ranges on the npm versions; pnpm-lock.yaml holds the exact resolution.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Every
@systemfsoftwarepackage is published to npm through trusted publishing, so this repository stops building them as local tarballs.file:.depsoverrides,mkProducerTarballs, the.depsdirectory handling and the dev shell tarball hook, plus the flake inputs that only fed them.workspace-tarballsstays.pnpm-lock.yamlis re-resolved from npm.pnpm add.