-
-
Notifications
You must be signed in to change notification settings - Fork 929
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 16.0.0 #7374
Comments
@jeddy3 Thanks for your consideration. I'll be available 6-10pm JST on Thursday or Friday this week. |
Let's shoot for Friday, as I'm freer that UK morning. |
Okay. I'll prepare the release stuff by Friday. |
@jeddy3 I'm starting the release now. 🚀 |
Oops. I forgot PR #7376 is still open. I'll wait for it. |
@ybiquitous I've approved #7376 |
I've merged #7358. I'll publish 16.0.0 now. |
npm & GitHub release published 🎉 |
Yep, "stylelint.io update" has not started yet. |
The packages and website are now published! 🎉 However, some contributors told me the type definitions had a bug, so I'll fix it soon and release a patch version @jeddy3 Could you tweet as the last task of this release instead of me, please? |
guys after update to 16.0.0 im getting this error
Regards |
see #7322 (comment) |
@newives what should i do ? i dont get it, thx |
Waiting for stylelint-scss to be upgraded stylelint-scss/stylelint-scss#894 (comment) |
@newives Thanks. Yes, stylelint-scss needs to deal with Stylelint 16.0.0 breaking changes. |
ohhh right, so i would need to wait, is there any workaround ? or should i do a downgrade ? |
@eduardocque It seems to be no workaround. You should keep 15.x. |
alright, thanks i will do that |
@jeddy3 I'll tweet the 16.0.0 announce now since a contributor will send a PR to fix the type problem. |
@ybiquitous I just saw your message now. I can tweet unless you're already on it? |
Ah, I've just tweeted right now. 😅 All tasks for this release are done! Thanks a lot for your contributions! 🎉 |
The tweet looks good; thank you! |
My tweet may be a bit unnatural. Please feel free to add extra tweets. 😅 I'm closing this issue. Please open a new issue if you have problems with 16.0.0. |
Thank you to everyone who contributed to this release: joining the discussions, committing code, reviewing pull requests, testing the prereleases, triaging issues and all the other bits we volunteer to do! And a special thank you to @ybiquitous , who tirelessly drove our migration to ESM over the past year. It was a colossal effort. |
Congratulations! |
I believe we're ready to release 16.0.0 once we:
Steps:
@ybiquitous Thank you so much for all your efforts. Would you like to do the release, as you've contributed so much to it? I can support the process UK time tomorrow, Thur or Friday this week. I believe UK morning is Japan evening; which evening suits you best?
The text was updated successfully, but these errors were encountered: