-
-
Notifications
You must be signed in to change notification settings - Fork 355
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
Where is the changelog for v15 beta releases? #1236
Comments
nyc 15 is released from the Up to you if you want to upgrade now or wait until the final release. Testers are appreciated, I think things are generally stable. |
Thanks. Consider making this more discoverable? Maybe a link to the issue in the CHANGELOG or the README? (Edit: #1237) To be clear, my scenario is I'm already on 15.0.0-beta.0, I get a Dependabot PR to upgrade to 15.0.0-beta.1, and I have absolutely no way to find out what changed in order to decide if I should merge the PR. An issue among 63 open issues is not exactly the most discoverable changelog. Just my two cents! |
Information about the next version in development, which is published to the NPM registry without git version tags and without CHANGELOG entries, is tracked in an open Github issue. This is not very discoverable on its own. This makes it more discoverable but linking to it from the master CHANGELOG. Closes istanbuljs#1236.
I've pinned #1104 so it will appear at the top of the issues list, I think this should be adequately discoverable. Just so you know the plan is that the final release will be pretty soon at which point the final changelog will be pushed to |
There are no git release tags, no entries in CHANGELOG.md, no version commits on master, and no special v15 branch. I honestly don't even understand where the v15 beta versions in npm are coming from. Is it moving to a new repo? Or is someone manually publishing version to the npm registry without tagging version in git?
How do I know whether to upgrade in my repos?
Thanks!
The text was updated successfully, but these errors were encountered: