Masafumi Koba

Due to #6358, there is a conflict. Can you please fix it?

@cordis-dev Thanks for opening the issue and using the template. I can reproduce the bug via the following code: ```js const selectorParser = require('postcss-selector-parser'); selectorParser().processSync('| h1', { lossless: false });...

Perhaps the same problem as https://github.com/postcss/postcss-selector-parser/issues/266

@calebepaglioza Thanks for using the template. Can you please provide a minimal reproduction repository so that we can look into the problem? Also, can you reproduce it on the command-line,...

I'm afraid that I cannot reproduce the error. Can you reproduce and share it in your personal and public repository, including minimum dependencies and source files?

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.

@jeddy3 Thanks for opening the issue. I agree with the deprecation included in a major release. 👍🏼

It seems that publishing on CI (GitHub Actions) is now available via **automation token**: https://github.blog/changelog/2020-10-02-npm-automation-tokens/ By this feature, I expect we can realize the complete automation of npm publishing!

@JounQin Thanks for the interesting suggestion. The [Node.js doc says](https://nodejs.org/api/corepack.html): > Corepack is an experimental tool But can we stably use the tool? --- > * remove `package-lock.json` from git,...

@bennypowers Thanks for the interesting suggestion. Is this suggested feature related to [Community Conditions Definitions](https://github.com/nodejs/node/blob/HEAD/doc/api/packages.md#community-conditions-definitions) in the Node.js documentation?