Release 15.7.0

[ybiquitous]

• stylelint release
• [] stylelint-config-recommended update/release
• [] stylelint-config-standard update/release
• stylelint.io update
• stylelint-demo check
• tweet

We'd like to do an urgent patch release for Cosmiconfg 8.2.0 breaking:

• Bump cosmiconfig from 8.1.3 to 8.2.0 #6893
• Segmentation fault (core dumped) #6898

The current changelog is here.

[ybiquitous]

Could be a fix:

• Fix Segmentation fault errors for Cosmiconfig 8.2 #6902

[ybiquitous]

I'll include the PRs below:

• Spellcheck on CI #6890

[ybiquitous]

I've changed the release version to 15.7.0 because it includes an addition (#6896).

[ybiquitous]

All done! 🎉

Thank you all so much for your contributions and efforts!

[mattxwang]

In terms of a post-mortem (which we can move to another issue), was there anything wrong with how we/I released 15.6.3? I wonder if there's something we could do to better test for these types of issues?

(for example, maybe I was too hasty releasing 15.6.3?)

[ybiquitous]

Hum, it's an interesting suggestion, but I believe we couldn't find this segmentation fault problem on the v15.6.3 release, because Cosmiconfg v8.2.0 was released on yesterday (June 5).

[ntwb]

It would be interesting to explore options available for when a dependabot PR fails such as this instance #6893

There's Slack & email GitHub actions notifiers, but maybe there are some actions that would add a comment pinging the @stylelint/contributors / @stylelint/owners teams on the PR alerting to the possibility that a patch or minor dependency bump is breaking CI

[ybiquitous]

The idea of pinging the teams sounds good to me. 👍🏼
However, it may be better to ping @stylelint/owners to avoid too many notifications to many contributors.

In addition, I suggest inviting @mattxwang and @romainmenke to the owners team. They have made great efforts for Stylelint.

What do you think? @stylelint/owners
(sorry for pinging here since GitHub's private discussion is gone now)