Skip to content
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

Can the latest changes be released? #996

Closed
bdwain opened this issue Jul 16, 2017 · 11 comments
Closed

Can the latest changes be released? #996

bdwain opened this issue Jul 16, 2017 · 11 comments

Comments

@bdwain
Copy link
Contributor

bdwain commented Jul 16, 2017

I'm currently blocked from using the latest webpack-dev-server until #980 is released. it was fixed since the last release but there has not been another yet.

Is there anything preventing a patch (or minor) release with the latest changes since 2.5.1?

@joshwiens
Copy link
Member

joshwiens commented Jul 16, 2017

The host check can simply be disabled in the interim as mentioned in this comment

As to a release, I'll ping someone and ask.

@bdwain
Copy link
Contributor Author

bdwain commented Jul 16, 2017

@d3viant0ne but the change is what exposes the option on the cli, right? so i'd have to change my build process to not use the cli in order to use that option? that's what i'm trying to avoid.

@joshwiens
Copy link
Member

I put out a request in slack, we'll get a patch version out.

@bdwain
Copy link
Contributor Author

bdwain commented Jul 17, 2017

thanks @d3viant0ne !

@bdwain
Copy link
Contributor Author

bdwain commented Jul 18, 2017

any word on this?

@bdwain
Copy link
Contributor Author

bdwain commented Jul 19, 2017

@SpaceK33z is it possible to get a patch release with the latest master? I've seen a few other issues that would also be resolved just with the latest master being released.

@bdwain
Copy link
Contributor Author

bdwain commented Jul 22, 2017

It's been a week now and I know a lot of people are blocked by this. Releasing what's already in master seems like a simple request and it's a little frustrating that it's taking this long.

@d3viant0ne was there any word when you asked the slack channel to do a release?

@joshwiens
Copy link
Member

@SpaceK33z - Is a.f.k with r.l business.

I don't have write nor publish access on this side of the house, so unfortunately all I can do at this point is ask which I have done twice.

@bdwain
Copy link
Contributor Author

bdwain commented Jul 22, 2017

@d3viant0ne well thank you for putting in the effort. i do appreciate it.

it seems like more people need write access since @SpaceK33z seems like a bottleneck for releases and when he's got other things going on nothing can get done. not sure where the best place to suggest that would be but it seems like the solution to the current problem.

@SpaceK33z
Copy link
Member

I released webpack-dev-server@2.6.0. @bdwain you seem to imply I am the only one who can release, but note that there are 4 more people who have npm publish rights.

@bdwain
Copy link
Contributor Author

bdwain commented Jul 25, 2017

thank you for doing the release @SpaceK33z. I was just suggesting that more members be given write/publish access since I know you're all busy and can't always respond ASAP, but trivial requests can often cause issues for many people at a time.

I appreciate all of the hard work you and everyone else put into this project and I'm sorry if I made it sound like that wasn't the case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants