-
-
Notifications
You must be signed in to change notification settings - Fork 936
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.4.0 #6743
Comments
@mattxwang Thanks for opening this issue. I think it's OK to release 15.4.0 (maybe this weekend).
Unfortunately, you don't have permission to publish packages to the npm registry, and I cannot grant you permission due to my lack of rights. 😓 So, I'll take over at this time. I appreciate your proposal. 😄 |
Merged. 👍🏼 So, we can ship our standard config together: |
I'd like to include the following in v15.4.0: |
Sounds good, just dropped a review. for stylelint/stylelint-config-standard#275, would you like me to open a PR in the repo to turn it on? Happy to do so, but not sure if it's already in progress. |
@mattxwang Thanks for your proposal. Please do so! |
It might be good timing to publish also |
@mattxwang Sorry for my misunderstanding. I just invited you to publish packages: Also, I just removed inactive maintainers from these packages. |
No worries at all! Confirming on my end that I've received the invitations. Would you prefer to continue taking point on this release? Happy to help out however possible! |
@mattxwang Could you try the release workflow if you are available this weekend? Our maintainer guide should help you. I guess you don't have access to our Twitter account, so I'll do only the last job of tweeting the announcement instead of you. (@jeddy3 manages all accounts related to Stylelint, not me) Feel free to ask me if you have any questions. |
Sounds good, will do! |
Hi @ybiquitous, sorry to bother again - unfortunately, I don't have permissions to force push to |
Closes #275; also ref: stylelint/stylelint#6743
@mattxwang No problem. I just changed the repo setting. Can you try it again? |
Hm, no dice @ybiquitous - same error as before (protected branch hook declined). Tried |
Sure!
|
Thanks. Is the same error raised when running (BTW, we should avoid force-push to the main branch 😅 ) |
Hm, so all the steps to publish to When I first ran Now, my
If I run Any advice on what to do? Could it be that the branch protection rule is "more important" than the branch permission you sent above? I know repositories have a feature that prevents admins from force-pushing as well.
Agreed, it felt a bit strange to type this out. I'll stick to |
OK, you are now admin in the repo. Can you try push again? |
Gotcha, that worked - just ran |
On a related note - I'm also not able to do the same for stylelint-config-standard (stylelint/stylelint-config-standard#284). Is a temporary admin the solution that works in this situation? Or, would you prefer to explore a different option (since it certainly feels awkward)? |
I just updated the following repos' settings again to make things simple:
|
@mattxwang Sorry for the inconvenience. 🙇🏼 I will recommend you for an owner-team member when @jeddy3 comes back, since you have a passion for Stylelint! |
Haha, not a problem at all - very sympathetic, onboarding new people and permissions is always tricky!
Aw, thank you! Also understand if that doesn't end up being possible for whatever reason (I am still very new in the grand scheme of things); just excited to help out however I can 😊 |
After merging stylelint/stylelint.io#311, I've verified that the site has been updated (ex the Changelog has been updated, the text for I think all that's left is now the tweet, unless I've missed anything else. Thanks for your timely support @ybiquitous! |
@mattxwang Congrats on your first release! |
Tweet done! 🎉 Thank you so much for your contribution and support, everyone! |
Following up from the conversation in #6725. To summarize, we have a new rule, new CLI flag + new alias, one rule bugfix, and one performance fix. See the in-progress changelog.
We could wait on #6742 depending on its complexity; curious for other thoughts!
(I've never done a release before, though I'm happy to take it up if others don't have time. I may not have some permissions though!)
The text was updated successfully, but these errors were encountered: