docs: link to next tracking issue in changelog #1237
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
|
Our changelog is auto-generated so I cannot merge this change. The plan is that nyc is not far from final release. In the future I will make a point to always pin the 'New Pending Release' issue so it is more discoverable, I think that will be adequate. Also note that side-publishing is only done for semver-major beta releases. In the case of for example 15.0.1 although we will briefly publish to npm under the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 by linking to it from the master CHANGELOG.
Closes #1236.