[intellild]

Publish the Rspack fork as rspack_lightningcss, starting the Rust crate at 0.1.0, with manually triggered Rust and npm/CLI/WASM release workflows.

• Rename the main Rust crate and update imports, examples, dependency references, the lockfile, and documentation.

• Keep the standalone release-crates workflow with publish preflight checks and a dry_run option. Only the main crate is published; helper crates use existing crates.io releases.

• Keep the manual release workflow for npm, CLI, and WASM packages, including installed-tarball checks and the Rust release workflow call. Both release entry points support dry_run; neither runs automatically on pushes or tags.

• Pin CI actions to commit SHAs and update Binaryen to 133 for WASM test builds.

• Preserve the upstream README body unchanged and add the fork's purpose, package names, versioning, and manual release instructions in a note at the top.

Usage example

cargo add rspack_lightningcss --version 0.1.0

use rspack_lightningcss::stylesheet::{ParserOptions, StyleSheet};

For example, dispatch release-crates with dry_run: true to package and compile rspack_lightningcss 0.1.0 without uploading it. Dispatch release with dry_run: true to additionally build and validate the npm, CLI, and WASM packages without publishing.

Validation

• Rust tests: 166 passed.
• Workspace compilation and version/dependency consistency checks passed.
• cargo publish -p rspack_lightningcss --dry-run --allow-dirty passed for version 0.1.0.
• Formatting, actionlint, and whitespace checks passed.
• Restored the manual release workflow exactly with its action pins and dry-run guards; actionlint and trigger checks passed.

No packages were published.

---

by OpenAI Codex

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	🔄 Running since 2026-10-21T07:30:52.620265Z	03b9c2a	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[codspeed]

Congrats! CodSpeed is installed 🎉

🆕 8 new benchmarks were detected.

You will start to see performance impacts in the reports once the benchmarks are run from your default branch.

Detected benchmarks

• stylesheet/parse[conditional-run]: 10.3 ms
• stylesheet/parse[large]: 27.5 ms
• stylesheet/parse[medium]: 6.9 ms
• stylesheet/parse[small]: 132.2 µs
• stylesheet/transform[conditional-run]: 13.6 ms
• stylesheet/transform[large]: 39.5 ms
• stylesheet/transform[medium]: 10 ms
• stylesheet/transform[small]: 230.7 µs

---