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

Version 1.3.1 not released properly #1086

Closed
TomWFox opened this issue May 22, 2019 · 14 comments · Fixed by #2180
Closed

Version 1.3.1 not released properly #1086

TomWFox opened this issue May 22, 2019 · 14 comments · Fixed by #2180
Labels
state:released Released as stable version state:released-alpha Released as alpha version state:released-beta Released as beta version

Comments

@TomWFox
Copy link
Contributor

TomWFox commented May 22, 2019

The 1.3.1 release seems to have not been published on either npm or Docker Hub...
Screenshot 2019-05-22 at 17 32 04
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...
Screenshot 2019-05-22 at 17 32 34

I'm not sure what's going on here, ideas? @acinader @dplewis

@dplewis
Copy link
Member

dplewis commented May 22, 2019

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 skip-cleanup: true in travis.yml so that webpack can be found.

@TomWFox
Copy link
Contributor Author

TomWFox commented May 22, 2019

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.

@dplewis
Copy link
Member

dplewis commented May 22, 2019

I don't have access either. @acinader Can you help us out?

@acinader
Copy link
Contributor

will try

@acinader
Copy link
Contributor

no joy. @flovilmart can you help?

@zenz
Copy link

zenz commented May 27, 2019

any updates?

@acinader
Copy link
Contributor

@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.

@zenz
Copy link

zenz commented Jun 5, 2019

I tried to add 1.3.1 from github url today. with command
yarn add https://github.com/parse-community/parse-dashboard#1.3.1

the process was succeed without any warning.
But after a service restart, while access the dashboard url, it just bring me a blank page.
and checking the errorlog, there's nothing.

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
https://github.com/zenz/parse-server-config

@dplewis
Copy link
Member

dplewis commented Jun 6, 2019

Dockerhub build is working again!

@TomWFox Can you do another release 1.3.2?

@TomWFox
Copy link
Contributor Author

TomWFox commented Jun 6, 2019

yep, I'll do it now

@dplewis
Copy link
Member

dplewis commented Jun 7, 2019

Closing via #1100

@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 4.2.0-alpha.1

@parseplatformorg parseplatformorg added the state:released-alpha Released as alpha version label Jul 4, 2022
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 4.2.0-beta.1

@parseplatformorg parseplatformorg added the state:released-beta Released as beta version label Sep 2, 2022
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 4.2.0

@parseplatformorg parseplatformorg added the state:released Released as stable version label Oct 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:released Released as stable version state:released-alpha Released as alpha version state:released-beta Released as beta version
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants