changeset-conventional-commits

changeset-conventional-commits

Generate changesets based on the conventional commits.

Use without adding as a dev dependancy

• Using pnpm

pnpm dlx changeset-conventional-commits

• Using npx

npx changeset-conventional-commits

Install

pnpm add -D changeset-conventional-commits

Usage

1. Make sure the project is setup with changesets.
2. Run pnpm changeset-conventional in the root.

This will generate changeset for each commit.

Note

This library is created based on this PR. There are issues created in changesets for this functionality and there is not update on this yet. So I created this library till that support is implemented.

Changelog

0.2.5

Patch Changes

• #27 e526cfb Thanks @mblackrittr! - fix: duplicate generation of changesets (#26)

  The same changesets were generated again, because the duplicate detection failed on trailing line breaks (\n) it got from git.

  <details> <summary>Details</summary> Imagine this data it holds while duplicate checking:

  const changesets = ...:

  // Data from Commits
  [
    {
      releases: [[Object], [Object]],
      summary: "chore(root): add two test packages\n",
      packagesChanged: [[Object], [Object]],
    },
  ];
  

  const currentChangesets = ...:

  // Data from Changesets
  [
    {
      releases: [[Object], [Object]],
      summary: "chore(root): add two test packages",
      packagesChanged: [[Object], [Object]],
    },
  ];
  

  Truncating the linebreak at line 165 of src/utils/index.ts fixed it:

  const compareChangeSet = (a: Changeset, b: Changeset): boolean => {
    // return a.summary === b.summary && JSON.stringify(a.releases) == JSON.stringify(b.releases);
    return (
      a.summary.replace(/\n$/, "") === b.summary &&
      JSON.stringify(a.releases) == JSON.stringify(b.releases)
    );
  };
  

  </details>