-
Notifications
You must be signed in to change notification settings - Fork 842
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 script updates #1865
Comments
Related: #1109 |
👋 Hey there. This issue hasn't had any activity for 180 days. We'll automatically close it if that trend continues for another week. If you feel this issue is still valid and needs attention please let us know with a comment. |
This is definitely still a thing. |
👋 Hey there. This issue hasn't had any activity for 180 days. We'll automatically close it if that trend continues for another week. If you feel this issue is still valid and needs attention please let us know with a comment. |
release.js does not ensure the local master branch is up to date with upstream's HEAD and that the working space is clean, nor does it verify that all latest dependencies are installed/built locally. Both of these individually, and certainly together, mean a release could be missing changes (at best) or provide an incomplete or broken build.
The text was updated successfully, but these errors were encountered: