Skip to content

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

Closed
legobeat opened this issue Dec 4, 2023 · 4 comments
Closed

Release 5.28.1 #4229

legobeat opened this issue Dec 4, 2023 · 4 comments

Comments

@legobeat
Copy link
Contributor

legobeat commented Dec 4, 2023

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.

@juanpicado
Copy link
Member

What do you mean extacly, do you refer to docker image only?, that commit is from master, v5 lives on branch 5.x.

@legobeat
Copy link
Contributor Author

legobeat commented Dec 5, 2023

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 npmjs.org. The docker update is not related to this.

I see v5.28.0 has just been released, so updating this issue accordingly.

@legobeat legobeat changed the title Release 5.27.1 Release 5.28.1 Dec 5, 2023
@legobeat
Copy link
Contributor Author

legobeat commented Dec 5, 2023

I realized now that you're releasing production releases from v5.x while master seems to be more of a dev-branch - so I guess fixes merged on master will have to be backported as well?

Is there a timeline/intention for releasing 6.0.0 at some point?

@juanpicado
Copy link
Member

juanpicado commented Dec 6, 2023

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.

@verdaccio verdaccio locked and limited conversation to collaborators Dec 6, 2023
@juanpicado juanpicado converted this issue into discussion #4237 Dec 6, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Projects
None yet
Development

No branches or pull requests

2 participants