yarn-lock-changes
yarn-lock-changes copied to clipboard
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).
Intro: yarn.lock file may contain several versions of the same dependency. When adding/upgrading packages using yarn, you sometimes end up not with an upgrade, but with an additional of another...
Example for #42
Hi! I'm getting the error `Error: Resource not accessible by integration` when the action runs on a PR created by a GitHub integration (dependabot). This makes the CI fail, I...
When the default branch has a `yarn.lock` with more recent packages than the branch that a PR is based on, `yarn-lock-changes` thinks that the PR is downgrading said packages even...
Currently all dependency changes are listed in summary comment. It will be nice to detect the depth of dependency and allow users to configure `maxDepth` via action inputs. This field...
Currently the table listing all the dependencies lists the dependencencies in alphabetical order based on the package name. This is fine for small diffs, but for large diffs it becomes...
Knowing how many duplicated packages is useful in PRs seperate from having them just listed as updated. (So maintainers can immediately ask contributors to run a yarn dedupe for example).