NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm, #1934 most downloaded on npm
A command line tool to easily install prebuilt binaries for multiple version of node/iojs on a specific platform
Latest stable
7.1.3
Last release 2 years ago
no release in 18 months
Ships unpredictably
gaps range from 3 weeks to 1.7 years
Some releases are documented
notes for 21 of 48 stable releases
Nothing withdrawn
no release was ever pulled
11 years old
48 releases · first in 2016
Drag across the ruler to compare, or tap a release to open it.
Bump napi-build-utils from 1 to 2 (#204) (`1bf4a15`) (Bailey Pearson)
Support environments where MD5 is prohibited (#191) (`9140468`) (Tomasz Szuba)
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Replace use of npmlog dependency with console.error (#182) (`4e2284c`) (Lovell Fuller).
Allow setting libc to glibc on non-glibc platform (#176) (`f729abb`) (Joona Heinikoski).
Upgrade to the latest version of detect-libc (#166) (`f71c6b9`) (Lovell Fuller).
Breaking: bump node-abi so that Electron 14+ gets correct ABI (#161) (`477f347`) (csett86). Drops support of Node.js < 10.
Move auth token to header instead of query param (#160) (`b3fad76`) (nicolai-nordic)
Inline no longer maintained noop-logger (#155) (`e08d75a`) (Alexandru Dima)
Support URL-safe strings in scoped packages (#148) (`db36c7a`) (Marco)
Support force & buildFromSource options in yarn (#140) (`8cb1ced`) (João Moreno)
Restore local prebuilds feature (#137) (`dc4e5ea`) (Wes Roberts). Previously removed in #81 / `a069253`.
In one word: reciprocity. Spending a modest amount of time on writing a changelog saves every reader twice as much time.
On any project regardless of git practices, there will be mistakes, noise and miscommunication. That's only natural. If needed a project can move fast in git and slow down for the changelog. The release can wait 15 minutes more.
In git history, a new feature may get described in more than one way because it takes time to develop a vocabulary. Maintainers will merge imperfect pull requests to stop a lenghty back-and-forth. Contributors forget that the quality of their commit messages deteriorates over time as context is lost. And so on.
Writing the changelog is another feedback loop to think things through. A chance to look at the big picture: how do recent pull requests play together? Was anything missed? Does the version number accurately reflect changes? Perhaps changes are breaking in unforeseen ways. Or (rarer) the opposite of that, which could be a waste of semver-major signaling.
Don't take the easy way out with full automation. This results in poor changelogs, defeating their purpose.
Fixes empty --tag-prefix (#143) (@mathiask88)
--tag-prefix (#143) (@mathiask88)Breaking: don't skip downloads in standalone mode (`b6f3b36`) (@vweevers)
Replace mkdirp dependency with mkdirp-classic (@ralphtheninja)
mkdirp dependency with mkdirp-classic (@ralphtheninja)mkdirp dependency with mkdirp-classic (@ralphtheninja)Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
The following workflow is triggered by a tag and takes the changelog entry for that tag from CHANGELOG.md and creates a GitHub release with the same c
The following workflow is triggered by a tag and takes the changelog entry for that tag from CHANGELOG.md and creates a GitHub release with the same content. The anton-yurchenko/git-release action that is used here also supports uploading assets to the GitHub release.
name : Release on : push : tags : [ ' * ' ] permissions : contents : write jobs : release : name : Release runs-on : ubuntu-latest steps : - name : Checkout uses : actions/checkout@v2 - name : Create GitHub release uses : docker://antonyurchenko/git-release:latest env : GITHUB_TOKEN : ${{ secrets.GITHUB_TOKEN }}
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Common Changelog has no opinions on Markdown formatting. The Markdown examples in this document follow the hallmark style guide.
Common Changelog has no opinions on Markdown formatting. The Markdown examples in this document follow the hallmark style guide.
Nothing published for this version
A change group must start with a third-level, text-only Markdown heading containing a category:
A change group must start with a third-level, text-only Markdown heading containing a category:
A release might have a separate upgrade guide or blog post that is considered essential reading. Other times a release may need to clarify its status,
A release might have a separate upgrade guide or blog post that is considered essential reading. Other times a release may need to clarify its status, when it was yanked or contains zero changes.
For these purposes a notice must be used. This is a single-sentence paragraph with otherwise arbitrary Markdown content. Adding Markdown emphasis markers is recommended. For example (links omitted):
UPGRADING.md ] ( UPGRADING.md ). ### Removed - Breaking: remove write() method from public API ( 01e3a64 )Notices are also useful to describe first releases (that have no changes). For example:
Use notices wisely, as they will be the first thing a reader sees at the expense of regularly structured content. There can only be one notice per release. If a notice pertains to code (rather than a release or associated artifacts) and has a suitable place outside of the changelog, write it there instead.
Nothing published for this version
Nothing published for this version
A release must start with second-level Markdown heading in the following format:
A release must start with second-level Markdown heading in the following format:
Where VERSION is a semver-valid version (without "v" prefix) matching a git tag (with optional "v" prefix). If the version is new then the changelog entry should be committed before creating the git tag. The DATE must be in the form of YYYY-MM-DD ( ISO 8601 ). For example:
The version should link to further information. If the project is hosted on GitHub, link the version to a GitHub release that should contain the same content as the changelog entry, alongside useful GitHub features like assets and the compare view. Preferably use reference-style links to keep the unrendered Markdown form of the changelog readable. Example
close() ## [ 1.0.0 ] - 2019-08-23 Initial release. [ 1.0.1 ] : https://github.com/owner/name/releases/tag/v1.0.1 [ 1.0.0 ] : https://github.com/owner/name/releases/tag/v1.0.0After the heading, a release must have Markdown content that is either:
One or more change groups ;
A notice followed by zero or more change groups .
Change groups are only optional if a notice explains why there aren't any. No other content is permitted, because a changelog is not a blog or detailed upgrade guide. Those have other goals and concerns and must be kept separate from the changelog.
Nothing published for this version
Nothing published for this version
Filename must be CHANGELOG.md . File content must be Markdown and start with a first-level heading:
Filename must be CHANGELOG.md . File content must be Markdown and start with a first-level heading:
Subsequent Markdown content must be zero or more releases, also referred to as changelog entries. Releases must be sorted latest-first according to Semantic Versioning rules, even if a release with a smaller version was published at a later time. This means that the semantically latest (and hence most important and frequently sought) release is at the top of the changelog. There must be an entry for every new stable release.
Nothing published for this version
A changelog is a file that contains a curated, ordered list of notable changes for each versioned release of a project. Its purpose is to make it easi
A changelog is a file that contains a curated, ordered list of notable changes for each versioned release of a project. Its purpose is to make it easier for consumers (and to a lesser extent contributors) to see precisely what changes have been made between two releases.
The consumers of software are human beings who care about what's in the software. They must be able to quickly understand the impact of a release. Semantic Versioning helps as a signaling mechanism but is not enough by itself. When software changes, people want to know why and how.
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.