Create new release to ship latest changes

[luminuu]

A month ago, changes were made to update deprecated rule names: 7816e56

Since no new release was created so far, we're still getting errors when using this package, for example: WordPress/twentytwentyone#188

I also get this warning on another project I'm working on.

Is it possible to create a new release to remove these warnings?

[luminuu]

Ping @ntwb - can you have a look on this? 🙂

[dero]

Hey! Any chance a new release could be created and published to fix this annoying issue, please?

[rodrigo-arias]

I mentioned the same here #266 without luck for now.

[ocean90]

The config has been migrated to @wordpress/stylelint-config though here's no npm release yet. Once the release is done you can switch to @wordpress/stylelint-config which includes the fix for the warning.

[ocean90]

@wordpress/stylelint-config is now available.

[rodrigo-arias]

@ocean90 I think the version published in NPM is not up to date. I can see the update in the master branch but not in the one tagged 18.0.0 which I suspect is the one that was published because it is what I get with NPM.

[sladomic]

Shouldn't the migration be mentioned in the README?

[ntwb]

Thanks @ocean90, closing this and apologies for not being available earlier to do this