New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 13.8.0 #5023
Comments
We're eagerly awaiting this release. Is there anything we can do to help? |
@jeddy3 same, we are really looking forward to this release, any ETA? Thank you for all your efforts! |
@jeddy3 same. For us its important that the future release includes a new version of @stylelint/postcss-markdown. This would fix vulnerabilities. Thanks to everybody for the efforts. Let me know if I can somehow help. |
The bottleneck in getting releases out is that the contributors who have the permissions to publish lack the time to do it. We've been giving more contributors permissions with the aim to reduce this bottleneck.
@jathak If you let me know your npm username, I can add you to the stylelint package and stylelint organisation (which houses postcss-markdown). The release process is documented here, but I can make time to be on call should you have any questions during the process. |
@jeddy3 My username on NPM is also jathak |
@jathak Thanks! I've sent you an invite to the stylelint organisation (that houses the postcss-markdown package, which will need to be released first) and the stylelint package. You'll need to enable 2FA. We made it a requirement after the ESLint security compromise a couple of years ago. |
I'll make time to do a release now. |
Done 🎉 Thank you to everyone who contributed new features and bug fixes to this release. |
@jeddy3 Thank you for releasing! 🥰 |
It's been a while since our last release. I should have time to put out one this week.
We should
Other than that, I don't see any pending pull request in this repo that are pressing. Can anyone else?
The text was updated successfully, but these errors were encountered: