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 15.9.0 #6959
Comments
@mattxwang Thanks for opening the issue! Agree 👍🏼 |
Hm, so I'm back at a previous problem I had -- I can run
Running either
Has something changed with my permissions from the last time I've cut a release (15.6.3, ~ 3 weeks ago)? @ybiquitous changed some team membership rules, so perhaps it's that? Interestingly, the release has been drafted with the right tag. |
@mattxwang Oh, sorry! I removed you from repository access a few days ago because I invited you to the Owners team. Now, I've regranted you. Can you retry it, please? I'm unsure why the Owners team members don't have admin access. 🤔 |
No worries at all, and thanks for the speedy response! Looks like that worked (see e56fc6c). Thanks! |
Sorry, I forgot to grant the Owner role @mattxwang and @romainmenke despite inviting them to @stylelint/owners. 🙇🏼 Now, they should have the Owner role. Please let me know if any problems. EDIT: I've removed Admin access to this repo of @mattxwang again since he has the Owner role already. |
I'll tweet the new release soon. |
All tasks are done! 🎉 @mattxwang Thanks for the releasing work! And thanks a lot for your great effort and contribution, everyone! |
stylelint-config-recommended updatestylelint-config-standard updateThe current changelog is at https://github.com/stylelint/stylelint/pull/6938/files, though as @Mouvedia has mentioned, the more important items might be three autofixes bugs for
declaration-block-no-redundant-properties
: #6956, #6957, #6958. I'll also do another pass through the keywords and see if anything else looks off.Happy to do all the release elements I have perms to (i.e. I'd need help with merging in the new stylelint.io + the tweet, but can do the rest).
The text was updated successfully, but these errors were encountered: