comment-parser is currently pinned to exactly 1.4.5 in this package's package.json dependencies. Version 1.4.7 contains a bug fix that downstream consumers would benefit from:
Could you either loosen the constraint to ^1.4.0 (or ^1.4.7) or bump the pin to 1.4.7? The exact pin currently blocks transitive updates via pnpm update --depth=Infinity, forcing downstream consumers to reach for pnpm.overrides to get the fix.
Thanks!
comment-parseris currently pinned to exactly1.4.5in this package'spackage.jsondependencies. Version1.4.7contains a bug fix that downstream consumers would benefit from:=(e.g. URLs in@see) is silently split into name/default syavorsky/comment-parser#190Could you either loosen the constraint to
^1.4.0(or^1.4.7) or bump the pin to1.4.7? The exact pin currently blocks transitive updates viapnpm update --depth=Infinity, forcing downstream consumers to reach forpnpm.overridesto get the fix.Thanks!