How to use the semantic-release/lib/definitions/plugins.generateNotes function in semantic-release

To help you get started, we’ve selected a few semantic-release examples, based on popular ways it is used in public projects.

Secure your code as it's written. Use Snyk Code to scan source code in minutes - no build needed - and fix issues immediately.

github pmowrer / semantic-release-github-pr / src / index.js View on Github external
NAMESPACE,
  'generateNotes',
  plugin => async (pluginConfig, config) => {
    const { pullRequests } = pluginConfig;
    const { nextRelease } = config;

    nextRelease.notes = await plugin(pluginConfig, config);

    await pullRequests.forEach(
      // Create "release" comment
      createChangelog(pluginConfig, { ...config, nextRelease })
    );

    return nextRelease.notes;
  },
  pluginDefinitions.generateNotes.default
);

module.exports = {
  verifyConditions: '@semantic-release/github',
  analyzeCommits: decoratePlugins(analyzeCommits),
  generateNotes: decoratePlugins(generateNotes),
};
github pmowrer / semantic-release-monorepo / src / index.js View on Github external
const analyzeCommits = wrapPlugin(
  NAMESPACE,
  'analyzeCommits',
  compose(logPluginVersion('analyzeCommits'), withOnlyPackageCommits),
  pluginDefinitions.analyzeCommits.default
);

const generateNotes = wrapMultiPlugin(
  NAMESPACE,
  'generateNotes',
  compose(
    logPluginVersion('generateNotes'),
    withOnlyPackageCommits,
    withOptionsTransforms([mapNextReleaseVersion(versionToGitTag)])
  ),
  pluginDefinitions.generateNotes.default
);

module.exports = {
  analyzeCommits,
  generateNotes,
  tagFormat: readPkg.sync().name + '-v${version}',
};

semantic-release

Automated semver compliant package publishing

MIT
Latest version published 27 days ago

Package Health Score

95 / 100
Full package analysis