fix(package): normalize publish metadata#19
Merged
Conversation
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.
What changed
Normalized the npm binary path and repository URL in
package.jsonto the canonical forms npm publishes.Why
The initial publish attempt was blocked by OTP and also reported that npm had auto-corrected the binary metadata. Committing the canonical values prevents publish-time mutation and makes the package contents deterministic.
Testing
npm run lint- passed.npm test- passed; 62 tests passed.npm pack --dry-run- passed with 43 package files and no metadata correction warning.opkexecutable reports version0.3.0.Risks
This changes package metadata only. The executable target and repository remain unchanged.
Follow-up
Publish
openpolicykit@0.3.0after this PR is merged and mark the npm roadmap item complete only after registry verification.