chore(op-sqlite): add files allowlist to package.json#21
Merged
Conversation
Restrict the published tarball to src/ and README.md so the build output, test fixtures, and stray dev files in the package directory don't leak into the npm package. Matches the intent of the root package's files allowlist.
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.
Summary
Add a `files` allowlist to packages/op-sqlite/package.json restricting the published tarball to `src/` and `README.md`. Brings op-sqlite in line with how the root package controls its tarball contents and prevents accidental dev/build leakage.
Why now
`@react-native-rag/op-sqlite@0.9.0` is stuck on a Sigstore/Rekor transparency-log conflict from the first failed publish attempt against the `v0.9.0` tag. The Rekor entry is immutable, so a republish from the same commit produces the same tarball hash → 409. This small content change is a real hygiene fix that also alters the tarball bytes enough for Rekor to accept a fresh entry.
Publishing plan after merge