Skip to content

PliegoCSS 0.1.0-rc.1

Pre-release
Pre-release

Choose a tag to compare

View all tags
@terrizoaguimor terrizoaguimor released this 20 Jul 18:01
v0.1.0-rc.1
073611f

PliegoCSS 0.1.0-rc.1

The first PliegoCSS release candidate is a standards-first CSS compiler, verifier, and evidence
pipeline written in Rust. It supports ordinary CSS adoption alongside an optional compile-time typed
Rust frontend.

Highlights

  • Audit ordinary CSS with human, canonical JSON, and SARIF findings.
  • Transform and minify standard CSS with explicit compatibility targets.
  • Compile typed pc! and pcx! Rust literals to deterministic static CSS.
  • Resolve TOML themes and DTCG 2025.10 token inputs.
  • Publish manifests, Source Map v3, token graphs, findings, and receipts as controlled groups.
  • Enforce bounded compatibility, accessibility, ownership, budget, and usage policies.
  • Inventory Sass, Tailwind CSS v4, CSS Modules, templates, configs, and plugin seams without executing
    their original toolchains.
  • Prepare exact, reversible Tailwind projections with hash-bound apply and rollback.
  • Provide a bounded stdio LSP and candidate VS Code/Neovim clients.
  • Package nineteen exact-version crates with Rust 1.85 as the library MSRV.

Verification

The release commit must pass the complete GitHub Actions matrix:

  • Ubuntu, Windows, and macOS;
  • Rust 1.85 and Rust 1.96;
  • package extraction and downstream replay;
  • bounded fuzzing;
  • WASM and compile-time diagnostics;
  • rustfmt, Clippy, rustdoc, provenance, and deterministic artifact checks.

Selected migration projections also have local Chrome and Edge computed-style evidence. This release
does not claim complete Tailwind parity, full browser coverage, or WCAG certification.

Install

Before crates.io publication, install the CLI directly from the release tag:

cargo install --git https://github.com/celiumsai/pliegocss --tag v0.1.0-rc.1 pliego-cssc

Once the registry publication completes:

cargo install pliego-cssc --version 0.1.0-rc.1 --locked

Important boundaries

  • This is a prerelease. Beta and experimental surfaces may change before 0.1.0.
  • Migration proposals are not automatically applied.
  • Missing runtime observations remain unknown; they are not proof of dead CSS.
  • Browser-required decisions remain explicit instead of being inferred by static analysis.
  • PliegoCSS emits static CSS and does not ship a browser styling runtime.

See the README, maturity map, and
release readiness document for complete scope and claims.

Assets 2
Loading