Release 14.4.0

[jeddy3]

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

Let's release once the following land:

• Add function-no-unknown #5865
• Fix false negatives for custom properties within var() in custom-property-pattern #5867
• Document allowEmptyInput option for the node js API #5883

And we've then prep pull requests for the configs as we'll be including function-no-unknown in recommended.

[jeddy3]

Prep pull requests ready for review at:

• https://github.com/stylelint/stylelint-config-recommended/pulls
• https://github.com/stylelint/stylelint-config-standard/pulls

[jeddy3]

I'm getting an ESLint error locally that'll stop me from publishing.

Is anyone else getting this locally or does anyone have any thoughts on what may be triggering it?

The CI is green.

jeddy3@MacBook stylelint % git pull
Already up to date.
jeddy3@MacBook stylelint % rm -rf node_modules 
jeddy3@MacBook stylelint % npm i

> stylelint@14.3.0 prepare
> husky install

husky - Git hooks installed

added 1082 packages, and audited 1083 packages in 37s

266 packages are looking for funding
  run `npm fund` for details

11 moderate severity vulnerabilities

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.
jeddy3@MacBook stylelint % npm run lint:js

> stylelint@14.3.0 lint:js
> eslint . --cache --max-warnings=0


/Users/jeddy3/Projects/stylelint/lib/rules/function-no-unknown/index.js
  6:35  error  "css-functions-list" is not found  node/no-missing-require

✖ 1 problem (1 error, 0 warnings)

jeddy3@MacBook stylelint % node --version
v16.13.2
jeddy3@MacBook stylelint % npm --version
8.3.2

/cc @gnuletik as connected to the function-no-unknown rule.

I'm hesitant to silence the warning in case it's legitimately flagging a potential issue with some system configurations.

[ybiquitous]

In my environment, it works. How about npm run lint:js -- --no-cache?

[jeddy3]

How about npm run lint:js -- --no-cache?

Bingo, thanks! That fixed it. First time I've encountered an ESLint caching issue.

I'll likely release later today.

[jeddy3]

Done 🎉. The demo didn't deploy automatically. I had to trigger a manual deployment. Not sure why. Let's keep an eye on it for the next release.

Thank you to everyone who added features, fixed bugs, wrote docs, refactored code, reviewed pull requests and so on for this release!

[ybiquitous]

@jeddy3 Thanks for the release! 🎉