-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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 5.28.1 #4229
Comments
What do you mean extacly, do you refer to docker image only?, that commit is from master, v5 lives on branch 5.x. |
Oh, I was hoping for a release including all the maintenance dependency-updates being published on I see |
I realized now that you're releasing production releases from Is there a timeline/intention for releasing |
Yes on branch 6.x, there is a discussion about it you can check why. Both branches benefit highly of any update from master (observe dependencies). Whenever 5.x is out of support 6.x will move to master and the idea is have one single branch, unfortunately I am not dedicated 100% and the world moves faster than my contributions :) so is some sort of workaround to make my life easier. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Would be nice to get a release with the dependency fixes and updates merged since
5.27.0
.376eb53 could affect users who extend the Docker image but that lives outside the npm package itself and otherwise it looks like all non-breaking maintenance changes.The text was updated successfully, but these errors were encountered: