v0.6.0

Changes visible for end-users:

• new failOnDowngrade optional input, when set to true action will fail when dependency downgrade has been detected, but will still post the detected changes comment
• SVG image labels URLs in bot comment has been shortened (via https://git.io/) to reduce the risk of reaching GitHub comment content charter limit

v0.5.0

Changes visible for end-users:

• support for large yarn.lock files (size above 1 MB)
• if generated comment will exceed GitHub comment character limit, image statuses will be replaced with plain text (to reduce the number of characters)

v0.4.0

Changes visible for end-users:

• if updateComment input is set to 'true', bot should remove the comment, if changes to the yarn.lock in PR has been reverted
• better validation of action inputs, especially booleans, (not only 'true', but also other values like 'yes' or 'on' will be resolved to true)

v0.3.0

Changes visible for end-users:

• lock changes table can be collapsed or expanded by users
• new collapsibleThreshold input which will determine if table should be expanded or collapsed by default
• new summary table will appear on the top of comment if count of changes is greater than collapsibleThreshold

v0.2.0

Changes visible for end-users:

• strategy for fetching base lock file has been changed, which enables action to run in private repositories
• bot now updates the comment by default, instead of creating new one on each commit,
• updateComment optional input, set it to "false" to enforce creating new comment
• new, updated and more verbose error messages

v0.1.0

Changes visible for end-users:

• switch to SVG status labels for readability and summary clarity
• support detection of "downgraded" dependency, earlier all mismatched versions were reported as "updated" (#7)

v0.0.3

Changes visible for end-users:

• do no post empty comment if there were no changes to the Yarn lock.

v0.0.2

Changes visible for end-users:

• removed debug console.log from action

v0.0.1

Yarn Lock Changes first release!