Skip to content

chore(deps): update dependency cssnano to v9 - #803

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/cssnano-9.x
Open

chore(deps): update dependency cssnano to v9#803
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/cssnano-9.x

Conversation

@renovate

@renovate renovate Bot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
cssnano ^8.0.5^9.0.0 age confidence

Release Notes

cssnano/cssnano (cssnano)

v9.0.1: v9.0.1

Compare Source

What's Changed

  • refactor: some small performance gains in #​1955

Full Changelog: https://github.com/cssnano/cssnano/compare/cssnano@9.0.0...cssnano@9.0.1

v9.0.0

Compare Source

v8.0.10: v8.0.10

Compare Source

What's Changed

  • Make charset normalization idempotent in #​1949

Full Changelog: https://github.com/cssnano/cssnano/compare/cssnano@8.0.9...cssnano@8.0.10

v8.0.9: v8.0.9

Compare Source

Bug fixes

Bug fixes coming by way of updating colordx and svgo to the latest release.

Full Changelog: https://github.com/cssnano/cssnano/compare/cssnano@8.0.8...cssnano@8.0.9

v8.0.8: v8.0.8

Compare Source

What's Changed

Bug Fixes
  • fix(postcss-minify-gradients): minify gradients using spec algorithm in #​1941

Full Changelog: https://github.com/cssnano/cssnano/compare/cssnano@8.0.7...cssnano@8.0.8

v8.0.7: v8.0.7

Compare Source

What's Changed

Bug Fixes
  • fix(cssnano): tighten option types in #​1919
  • fix(postcss-discard-empty): better optimize cascade layers in #​1924
Documentation
  • docs: add security information in #​1922
Website playground
  • feat(site): update playground to use a web worker in #​1918

Full Changelog: https://github.com/cssnano/cssnano/compare/cssnano@8.0.6...cssnano@8.0.7

v8.0.6: v8.0.6

Compare Source

What's Changed

Bug Fixes
  • fix(postcss-merge-rules): fix invalid merging in #​1893

  • fix(postcss-merge-rules): use webref data to perform a merge #​1897

  • fix(postcss-reduce-idents): do not break grid-template-areas in #​1898

  • fix: ensure correct repository URL in published packages in #​1900

  • fix(postcss-merge-longhand): improve longhand merging correctness in #​1907

  • fix(postcss-merge-longhand): add a fuzzer and fix the cases it found in #​1914

  • fix: improve selector minification in #​1915

Other Changes

Full Changelog: https://github.com/cssnano/cssnano/compare/cssnano@8.0.5...cssnano@8.0.6


Configuration

📅 Schedule: (in timezone Asia/Shanghai)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate

renovate Bot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
Scope: all 65 workspace projects
? Verifying lockfile against supply-chain policies (1848 entries)...
[WARN] Request took 10844ms: https://registry.npmjs.org/@types%2Fnode
✓ Lockfile passes supply-chain policies (1848 entries in 27s)
Progress: resolved 1, reused 0, downloaded 0, added 0
[ERR_PNPM_TRUST_DOWNGRADE] High-risk trust downgrade for "cssnano@9.0.0" (possible package takeover)

This error happened while installing a direct dependency of /tmp/renovate/repos/github/vuepress/ecosystem

Trust checks are based solely on publish date, not semver. A package cannot be installed if any earlier-published version had stronger trust evidence. Earlier versions had staged publish, but this version has trusted publisher. A trust downgrade may indicate a supply chain incident.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants