![Oracle Drags Its Feet in the JavaScript Trademark Dispute](https://cdn.sanity.io/images/cgdhsj6q/production/919c3b22c24f93884c548d60cbb338e819ff2435-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
elgg-conventional-changelog
Advanced tools
$ npm install elgg-conventional-changelog
Generate a changelog from git metadata, using these commit conventions.
View CONVENTIONS.md for a synposis of the conventions with commit examples.
Adapted from code originally written by @vojtajina, from grunt-conventional-changelog.
Simple usage:
require('changelog')({
repository: 'https://github.com/joyent/node',
version: require('./package.json').version
}, function(err, log) {
console.log('Here is your changelog!', log);
});
changelog(options, callback)
By default, calls the callback with a string containing a changelog from the previous tag to HEAD, using pkg.version, prepended to existing CHANGELOG.md (if it exists).
callback
is the second parameter, and takes two parameters: (err, log)
. log
is a string containing the newly generated changelog, and err
is either an error or null.
options
is the first parameter, an object. The following fields are available:
version
{string}
- The version to be written to the changelog. For example, {version: require('./package.json').version}
subtitle
{string}
- A string to display after the version title in the changelog. For example, it will show '## 1.0.0 "Super Version"' if codename '"Super Version"' is given. By default, it's blank.
repository
{string}
- If this is provided, allows issues and commit hashes to be linked to the actual commit. Usually used with github repositories. For example, {repository: 'http://github.com/joyent/node'}
commitLink
{function(commitHash)}
- If repository is provided, this function will be used to link to commits. By default, returns a github commit link based on options.repository: opts.repository + '/commit/' + hash
issueLink
{function(issueId)}
- If repository is provided, this function will be used to link to issues. By default, returns a github issue link based on options.repository: opts.repository + '/issues/' + id
from
{string}
- Which commit the changelog should start at. By default, uses previous tag, or if no previous tag the first commit.
to
{string}
- Which commit the changelog should end at. By default, uses HEAD.
file
{string}
- Which file to read the current changelog from and prepend the new changelog's contents to. By default, uses 'CHANGELOG.md'
.
log
{function()}
- What logging function to use. For example, {log: grunt.log.ok}
. By default, uses console.log
.
warn
{function()}
- What warn function to use. For example, {warn: grunt.log.writeln}
. By default, uses console.warn
.
types
{Object}
- A map of commit types to section headings.
This allows you to customize what sections will be included in the changelog.
By default, always includes {fix: 'Bug Fixes', feat: 'Features', breaks: 'Breaking Changes'}
Add new sections: {perf:'Performance'}
Rename a section: {feat:'New stuff'}
Alias two types to the same section: {feat: 'Features', feature: 'Features'}
BSD
0.1.2 (2014-05-06)
<a name="0.1.1"></a>
FAQs
Generate a markdown changelog from git commit metadata
The npm package elgg-conventional-changelog receives a total of 2 weekly downloads. As such, elgg-conventional-changelog popularity was classified as not popular.
We found that elgg-conventional-changelog demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 3 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.