Refresh third-party notices for the lockfile lightningcss closure #106
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/refresh-third-party-notices"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Regenerates THIRD-PARTY-NOTICES.md against the committed bun.lock with a clean frozen install.
The previous file was generated from a node_modules that still carried the ten lightningcss 1.32.0 platform binaries alongside 1.33.0. A lockfile-consistent install keeps only the 1.33.0 platform set (plus the nested 1.32.0 core that @tailwindcss/node pins), so the accurate closure is 251 packages. Both lightningcss core versions and all eleven 1.33.0 platform packages remain fully documented with their MPL-2.0 licences. Generated with pinned Bun 1.3.14; notices:check passes.
kReview review
Verdict: no findings
No findings to address in the reviewed diff.
No meaningful defects are established by the visible notice regeneration changes.
Reviewed by kReview at
79b1043da5. This comment is conservative and based only on the PR diff, metadata, and supplied repository context.Est. cost ~$0.55 (259.1k in / 799 out / gpt-5.6-sol).