docs: write README in maintainer voice - #10
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
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.
What changed
sharp0.35.3 through the existing npm override mechanismWhy
The README used detached, defensive wording that obscured authorship. During the
PR check, npm also reported newly disclosed high-severity libvips issues through
the previous
sharprelease. The override updates that transitive dependencywithout forcing a breaking Next.js change.
Validation
npm ci --ignore-scriptsnpm run check(lint, typecheck, 42 unit tests, build, and 2 render tests)npm audit --omit=dev --audit-level=high(0 vulnerabilities)git diff --check