Release @logicsrc/openprd 0.2.0 to npm - #145
Open
ralyodio wants to merge 1 commit into
Open
Conversation
Published as @logicsrc/openprd@0.2.0 — the first release of this package, and the first carrying OpenPRD 0.3 (Tech Stack and Monetization, #144). Two things had to change for the publish to be usable: - The @logicsrc/validators dependency was `file:../validators`. npm publishes that spec verbatim, so every install outside this monorepo would have failed to resolve it. It is now `^0.1.0`, which is what is on the registry; npm workspaces still links the local package for development, since 0.1.0 satisfies the range. - Added a README. Without one the npm page reads "No README data found", which is a poor landing surface for the reference implementation of a public standard. @logicsrc/schemas already ships one. Verified by installing 0.2.0 from the registry into an empty project: it resolves @logicsrc/validators@0.1.0 and @logicsrc/schemas@0.1.0, and the runtime reports OPENPRD_VERSION 0.3 with ten sections, eight for 0.2. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017XRNNm6pK6nPi7rJ6bJNHu
ThreatCrush Security Scan21 finding(s) HIGH/CRITICAL: 3 | MEDIUM: 9 | LOW: 9
Snippets are redacted; ThreatCrush never prints matched credential material. |
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
1 participant
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.
@logicsrc/openprd@0.2.0is published to npm. This PR syncs master to what the registry now has.The first release of this package, and the first carrying OpenPRD 0.3 (
Tech Stack+Monetization, #144).Why the manifest had to change
@logicsrc/validatorswasfile:../validators. npm publishes that spec verbatim, so any install outside this monorepo would have failed to resolve the dependency — the package would have been on the registry and uninstallable. Now^0.1.0, which matches what's published. npm workspaces still links the local package for development, since0.1.0satisfies the range.@logicsrc/schemasalready ships one;@logicsrc/validatorsdoes not, and shows exactly that.Verification
Installed
0.2.0from the registry into an empty project:packages/openprdtests: 79 passed against the bumped manifest.package-lock.jsonis unchanged — the workspace link resolves identically under the semver range.🤖 Generated with Claude Code
https://claude.ai/code/session_017XRNNm6pK6nPi7rJ6bJNHu