Bump postcss-discard-comments from 6.0.1 to 7.0.5

[dependabot]

Bumps postcss-discard-comments from 6.0.1 to 7.0.5.

Release notes

Sourced from postcss-discard-comments's releases.

v7.0.5

Bug Fixes

• Fix layer rule deduping cssnano/cssnano#1656

v7.0.4

Bug fixes

• fix(postcss-convert-values): preserve percent sign in border-image-width in cssnano/cssnano#1645

v7.0.3

Bug Fixes

• cssnano-preset-default: preserve SVG viewbox and title by default
• postcss-convert-values: preserve percent sign in arguments of color functions when needed
• postcss-ordered-values: preserve correct order in animation property
• postcss-minify-selectors: preserve quotes when escaping selector is required
• postcss-discard-comments: do not remove strings that only look like comments in selectors

Thanks to @​ota-meshi and @​seiyab for their contributions to this release.

v7.0.2

Bug Fixes

• fix invalid output in some cases where selectors contain comments

v7.0.1

Patch changes

Update postcss-calc dependency to latest version

v7.0.0

Breaking changes

This release drops official support for unmaintained long term support Node.js releases 14 and 16. It also drops support for non-long term support releases 19 and 21 and add support for Node.js 22. Only the package.json engines field has been updated. The code should otherwise be identical to the previous 6.1.2 release.

Ensuring support for older Node.js had become difficult as the GitHub actions runners are not available for the latest MacOS and recent pnpm also could not run on CI any more.

v6.1.2

Bug Fixes

• preserve correct order of gap and column-gap properties

Patch Changes

• update autoprefixer

v6.1.1

Patch changes

• update selector parser
• in the minify font plugin, you can pass a function to determine whether a css variable is one of font, font-family, and font-weight to determine whether the variable needs to remove quotes.

v6.1.0

This release contains a lot of fixes to Browserslist support thanks to @​colinrotherham

... (truncated)

Commits

• c847b6b Publish cssnano 7.1.2
• 72dd9c9 fix: update browserslist
• 19849ba chore: update dev dependencies
• ad02c7c chore: use npm trusted publishing
• f31273c fix: enhanced recognition of css comments (#1730)
• bd3b251 chore: update GitHub actions
• bba3b5f chore: update development deps
• 53c4033 test: switch to built-in Node.js test coverage
• ff17fd3 chore: update development dependencies
• c9e493c chore: update pnpm
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for postcss-discard-comments since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[shopify-shipitnext]

🔎 View this PR in Shipit Next.

ℹ️ Expand to learn how to deploy and handle emergencies using Shipit Next

Overview

Shipit Next will merge your code on your behalf because this repository uses Shipit Next and its merge queue.

To ship this PR, you can either:

• Comment /shipit to enqueue this PR for merging.
• Go to this PR in Shipit Next and click on the "Ship It" button in the top-right corner.

Comment Commands

• /shipit: Enqueue this PR into the merge queue where it will eventually be merged and deployed.
• /cancel: Eject this PR from the merge queue and rebuild PRs that were enqueued after this PR.
• /shipit --jump-queue: Enqueue this PR at the top of the merge queue where it will be included in the next deploy. Use this for non-emergency situations.
  - Emergency handling procedure for this command can be found here.
• /shipit --emergency: Merge this PR directly into main and deploy to all environments once all require_for_emergency CI checks pass. Please be aware that changes deployed with this command will not be automatically rolled back.
  • Emergency handling procedure for this command can be found here.

Commands exclusive to Deploy Before Merge

• /cancel --emergency: Eject this PR from the merge and rollback any deployments containing this PR.

---

Documentation

• ℹ️ You can read how the merge queue works in Vault here.
• ⚠️ Emergency handling documentation in the Vault describes how to handle emergencies, e.g. failed canaries, broken code in production, etc.

Questions or feedback?

• Non-urgent questions can be submitted in our Discourse.
• Feedback can be submitted in our frustrations Google form.
• If you have feature requests, you may add them or vote for them in our GitHub repository.