Masafumi Koba

Ah, sounds good. 👍🏼

The [`v15`](https://github.com/stylelint/stylelint/tree/v15) branch is now available as a destination to push this commit. So we can go forward with this PR.

@mattxwang I'm not sure, but probably the Changeset GitHub App doesn't work on branches except for `main`. We can run `npx changeset add` locally to add a changelog entry instead.

@jeddy3 What can we include other changes with the next major release than dropping the Node.js 12 support? Have we discussed it?

@jeddy3 @Mouvedia Thanks for the feedback. I agree with the following idea: > We should try to incorporate as many of our breaking changes as major releases can be troublesome...

FYI, npm@9 seems to drop Node.js 12 support. See https://github.com/npm/cli/releases/tag/v9.0.0-pre.0 > `npm` is now compatible with the following semver range for node: `^14.17.0 || ^16.13.0 || >=18.0.0`

@Mouvedia Thanks for the proposal. Umm... According to the [guideline for built-in rules](https://stylelint.io/user-guide/rules/about), I don't think the proposed rule is "generally useful; not tied to idiosyncratic patterns". 🤔 Without depending...

It seems to me this issue is historical. The `meow` package, which is used internally for CLI, exits with `2` when specified flags are invalid: https://github.com/sindresorhus/meow/blob/dc7dae4820bfc7397193a92833487d47f82c7411/index.js#L184

@JounQin Thanks for the proposal. I have some questions. 1. We have the following workflow already for updating the `CHANGELOG.md` file, but will your proposed tool replace with it? https://github.com/stylelint/stylelint/blob/4772851c0a1745db03f149ac35a2de6fe375c369/docs/maintainer-guide/pull-requests.md?plain=1#L27-L32...

@JounQin Thanks for the answers. Sounds good to me. 👍🏼