Creates a comment inside Pull Request with the human-readable summary of changes to the Yarn lock file. Works with every Yarn version (classic and berry).
MIT License
Bot releases are hidden (Show)
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 tov0.11
, to use the latest action prior this release:- name: Yarn Lock Changes uses: Simek/[email protected]
Published by Simek 12 months ago
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.
Published by Simek about 1 year ago
add groupByType
boolean config option to group row in the comment table by the change type, the following order will be used:
The dependencies within the groups will still be ordered alphabetically.
Published by Simek over 2 years ago
Published by Simek over 2 years ago
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.
Published by Simek over 2 years ago
None, see notes below.
This version includes the switch to new and internal Yarn lock parser, which introduction aims for better extensibility and general action performance. At least for now, the new parser outputs the same data structure as the official Yarn package, so there should not be any visible changes for the end-users.
Published by Simek over 2 years ago
Published by Simek about 3 years ago
Published by Simek about 3 years ago
If the action fails in your repository for the Dependabot PRs please check the "Common Issues" section in the Readme, which includes the guide how to update the workflow file and why you need to do this to fix the issue.
Published by Simek over 3 years ago
path
input is set to the custom value, the bot comment will now include the note about lock file location, this should help to differentiate the comments when multiple locks have been changeg within the same Pull Request@actions/core
package helper method getBooleanInput
, which only supports the reduced set of YAML Boolean values, so this might be considered as breaking change for the small portion of users who were using yes/no
, on/off
or y/n
input values (however, the error message will be quite descriptive, so it should be easy to migrate the workflow setup)Published by Simek over 3 years ago
failOnDowngrade
optional input, when set to true
action will fail when dependency downgrade has been detected, but will still post the detected changes commentPublished by Simek over 3 years ago
yarn.lock
files (size above 1 MB)Published by Simek over 3 years ago
updateComment
input is set to 'true'
, bot should remove the comment, if changes to the yarn.lock
in PR has been revertedboolean
s, (not only 'true'
, but also other values like 'yes'
or 'on'
will be resolved to true
)Published by Simek over 3 years ago
collapsibleThreshold
input which will determine if table should be expanded or collapsed by defaultcollapsibleThreshold
Published by Simek over 3 years ago
updateComment
optional input, set it to "false"
to enforce creating new commentPublished by Simek over 3 years ago
Published by Simek over 3 years ago
Published by Simek over 3 years ago
console.log
from actionPublished by Simek over 3 years ago
Yarn Lock Changes first release!