Revert removed changelog entry

[jeddy3]

Which issue, if any, is this issue related to?

None.

Is there anything in the PR that needs further explanation?

We've consistently followed the conventions of:

• Fixed & Security = Patch
• Added & Deprecated = Minor
• Removed & Changed = Major

This pull request removes the inconsistent changelog entry, which isn't user-facing and is "patch" for "Removed".

[changeset-bot]

⚠️ No Changeset found

Latest commit: e0811bc

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[romainmenke]

Removed & Changed = Major

Good to know 🙇

---

This was initially :

Fixed: remove `postcss-media-query-parser` dependency

#6999 (comment)

Should it be reverted to that?

[jeddy3]

Should it be reverted to that?

I don't think so. It's not user-facing, and "Fixed: remove" will be inconsistent with the other entries in the changelog.

[romainmenke]

LGTM!

[ybiquitous]

Um... I acknowledge the inconsistency, but will not PR #6999 affect people, especially plugin authors using postcss-media-query-parser?

I think we should inform people about the removed dependency in some way. Any thoughts?

[jeddy3]

I don't think we need to as those changes were a refactor that didn't change our public API (for consumers and plugin authors). However, how about we include a second tweet as part of the release to let people know about and draw attention to the new parser? Something along the lines of:

"Under the hood, we've replaced our media query parser with @romainmenke's more modern and spec-compliant one. If you're a plugin author targeting media queries, we recommend using this parser too: https://www.npmjs.com/package/@csstools/media-query-list-parser"

That way people are informed and the changelog remains for our public API.

[ybiquitous]

That sounds good. 👍🏼