-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Version 1.3.1 not released properly #1086
Comments
I opened a PR for the docker issue. #1087 (whenever travis works again) For NPM, I'm not sure but looking at the travis logs there does seem like an issue. I'd recommend setting |
The Docker build still seems to be failing, I’m assuming there are some logs on Docker Hub but if they exist I can’t access them. |
I don't have access either. @acinader Can you help us out? |
will try |
no joy. @flovilmart can you help? |
any updates? |
@zenz no I currently don't have credentials for the dockerhub parse account, which will take some attention to resolve. Also, the issue that is preventing publishing will need to be diagnosed. I have not looked at in detail yet and it could be a few more days before I can. If anyone has some time to diagnose, that could be helpful. |
I tried to add 1.3.1 from github url today. with command the process was succeed without any warning. After more debuging. I found that this version 1.3.1 is not follow the same way which previous version does. It's not respect users settings. like I use SSL for secure transfer, it's working fine with versions before 1.3.0, but in 1.3.1, using same configuration, I will failed with in secure reason, this is why it brings the blank page. here's my configuration |
Dockerhub build is working again! @TomWFox Can you do another release 1.3.2? |
yep, I'll do it now |
Closing via #1100 |
🎉 This change has been released in version 4.2.0-alpha.1 |
🎉 This change has been released in version 4.2.0-beta.1 |
🎉 This change has been released in version 4.2.0 |
The 1.3.1 release seems to have not been published on either npm or Docker Hub...
It does sometimes take a while for the new version to be published to npm but it has been 18 hours so I'm guessing something is wrong.
The Docker build seems to have been failing since db559a8...
I'm not sure what's going on here, ideas? @acinader @dplewis
The text was updated successfully, but these errors were encountered: