codecov[bot]
commented
3 years ago Codecov Report
Merging #41 (9eb91d7) into master (080ed24) will not change coverage. The diff coverage is
n/a.
@@ Coverage Diff @@
## master #41 +/- ##
=======================================
Coverage 86.36% 86.36%
=======================================
Files 2 2
Lines 44 44
Branches 6 6
=======================================
Hits 38 38
Partials 6 6 Continue to review full report at Codecov.
Legend - Click here to learn more
Ξ = absolute <relative> (impact),ΓΈ = not affected,? = missing dataPowered by Codecov. Last update 080ed24...9eb91d7. Read the comment docs.
github-actions[bot]
This PR contains the following updates:
1.22.5->1.22.15Release Notes
yarnpkg/yarn
### [`v1.22.15`](https://togithub.com/yarnpkg/yarn/compare/v1.22.14...v1.22.15) [Compare Source](https://togithub.com/yarnpkg/yarn/compare/v1.22.14...v1.22.15) ### [`v1.22.14`](https://togithub.com/yarnpkg/yarn/releases/v1.22.14) [Compare Source](https://togithub.com/yarnpkg/yarn/compare/v1.22.13...v1.22.14) - Fixes false positives that would happen on non-win32 platforms ("Potentially dangerous call to ...") ### [`v1.22.13`](https://togithub.com/yarnpkg/yarn/releases/v1.22.13) [Compare Source](https://togithub.com/yarnpkg/yarn/compare/v1.22.12...v1.22.13) - Fixes a potential security issue where packages could run scripts even with `--ignore-builds` set (Windows only) - Fixes `yarn init -y2` w/ Corepack - `yarn set version stable` (and `canary`) will now defer to the stable & canary for upgrading the project ### [`v1.22.12`](https://togithub.com/yarnpkg/yarn/releases/v1.22.12) [Compare Source](https://togithub.com/yarnpkg/yarn/compare/v1.22.11...v1.22.12) Bogus release (published the wrong folder) ### [`v1.22.11`](https://togithub.com/yarnpkg/yarn/blob/master/CHANGELOG.md#12211) [Compare Source](https://togithub.com/yarnpkg/yarn/compare/v1.22.10...v1.22.11) This version fixes a problem where Yarn wasn't forwarding SIGTERM to the binary spawned via `yarnPath`. It also makes `yarn init -2` compatible with [Corepack](https://togithub.com/nodejs/corepack). The behaviour of `yarn init` (without `-2`) doesn't change. Remember that Yarn 1.x won't receive further functional improvements. We recommend you to switch to the recently-released 3.0, and to ping us on Discord if you find issues when migrating (also check our [Migration Guide](https://yarnpkg.com/getting-started/migration#why-should-you-migrate)). ### [`v1.22.10`](https://togithub.com/yarnpkg/yarn/blob/master/CHANGELOG.md#12210-and-prior) - Tweak the preinstall check to not cause errors when Node is installed as root (as a downside, it won't run at all on Windows, which should be an acceptable tradeoff): [https://github.com/yarnpkg/yarn/issues/8358](https://togithub.com/yarnpkg/yarn/issues/8358) ### [`v1.22.7`](https://togithub.com/yarnpkg/yarn/blob/master/CHANGELOG.md#1227) This release doesn't change anything and was caused by a publish issue. ### [`v1.22.6`](https://togithub.com/yarnpkg/yarn/blob/master/CHANGELOG.md#1226) - Running `yarn init` with the `-2` flag won't print the `set version` output anymore. - A new preinstall check will ensure that `npm install -g yarn` works even under [Corepack](https://togithub.com/arcanis/corepack). It doesn't have any effect on other setups.Configuration
π Schedule: At any time (no schedule defined).
π¦ Automerge: Disabled by config. Please merge this manually once you are satisfied.
β» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
π Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.