v0.14.1

Changes visible for end-users:

• omit empty rows in summary table

v0.14.0

Changes visible for end-users:

None, see notes below.

⚠️ Additional notes

This version includes action source and tests rewrite to TypeScript. Since the migration-related code changes have been kept to a minimum, there should be no visible changes for end users.

v0.13.0

Changes visible for end-users:

• drop Node 18 and Node 20 workflows support

  Node 20 is approaching its end-of-life date, and all Node 20 (and earlier) runners are currently deprecated on GitHub.
  Starting in early March, Node 24 will become the default runner version unless users specify a version manually. You can read more on the GitHub Blog:

  • https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Note

For Node <22 support, you can change the action version tag in your workflow to v0.12.0 , to use the latest action prior this release:

- name: Yarn Lock Changes
  uses: Simek/yarn-lock-changes@v0.12.0

v0.12.2

Changes visible for end-users:

• fix for status label images sizing

v0.12.1

Changes visible for end-users:

• improve slightly lock-files parsing performance

v0.12.0

Changes visible for end-users:

• drop Node 14 and Node 16 workflow support

  As stated in the previous release, from this major version upward, the Node 14 and Node 16 workflow support has been dropped, due to upgrade of @actions/github package.

Note

For Node <18 support, you can change the action version tag in your workflow to v0.11.0 , to use the latest action prior this release:

- name: Yarn Lock Changes
  uses: Simek/yarn-lock-changes@v0.11.0

v0.11.3

Changes visible for end-users:

• fix error while parsing lock files with optional name key in entries (thanks to @nathanforce for the issue report and initial fix)

---

Note

In the next major action release the support for Node 14 and 16 will be dropped because of the latest @actions/github release which drops the support for those engines due to Octokit packages update.

If you are running the action using different runner than the default one, it might be a good time to make sure that your workflow uses at least Node 18. Otherwise, the future Node version switch should be seamless for you.

v0.11.2

Changes visible for end-users:

• add groupByType boolean config option to group row in the comment table by the change type, the following order will be used:

  • Added
  • Updated
  • Downgraded
  • Removed

  The dependencies within the groups will still be ordered alphabetically.

v0.11.1

Changes visible for end-users:

• [Berry] fix error while parsing locally linked packages with no dependencies (thanks to @ValentinH for the issue report)

v0.11.0

Changes visible for end-users:

• action now includes support for parsing and diffing Yarn Berry (v2 & v3) locks

  Note If you notice any problems or experience failures while using action with newer locks, please let me know and fill an issue.