-
-
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
No information about new beta releases: hard to debug #340
Comments
Can you setup semantic release for the beta probably? |
Better? ;-) Far from perfect but better than nothing. With semantic-release it‘s not easy as I understand. |
This was referenced Aug 17, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There is no publicly available information about when new beta releases are published on npm and what changes are in them (or at least I couldn't find it). The version field in package.json is not updated, so there are no release commits. There are no git tags after beta 9.
My current problem: something that happened in beta 12 breaks my phantomjs tests (the screenshots are off position, this works perfectly in beta 11). Without knowing what was released as beta 12, or when betas 11 and 12 were released, it becomes very hard for me to debug the problem.
Help?
The text was updated successfully, but these errors were encountered: