search

traggo / server

self-hosted tag-based time tracking
https://traggo.net
GNU General Public License v3.0
1.21k stars 58 forks source link

Bump yarn from 1.19.1 to 1.22.17 in /ui #108

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps yarn from 1.19.1 to 1.22.17.

Release notes

Sourced from yarn's releases.

v1.22.17

No release notes provided.

v1.22.16

No release notes provided.

v1.22.15

  • Fixes an issue on Windows where relative scripts would fail to execute

v1.22.14

  • Fixes false positives that would happen on non-win32 platforms ("Potentially dangerous call to ...")

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

Bogus release (published the wrong folder)

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. 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).

1.22.10

(and prior)

Please check the changelog for details: https://github.com/yarnpkg/yarn/blob/master/CHANGELOG.md

For technical reasons, no prebuilt artifacts will be generated for this release. Please use npm install -g yarn to install it.

v1.22.5

No release notes provided.

v1.22.4

No release notes provided.

v1.22.3

No release notes provided.

v1.22.2

No release notes provided.

v1.22.1

No release notes provided.

v1.22.0

No release notes provided.

... (truncated)

Changelog

Sourced from yarn's changelog.

Changelog

Please add one entry in this file for each change in Yarn's behavior. Use the same format for all entries, including the third-person verb. Make sure you don't add more than one line of text to keep it clean. Thanks!

1.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. 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).

1.22.10 (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): yarnpkg/yarn#8358

1.22.7

This release doesn't change anything and was caused by a publish issue.

1.22.6

  • 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. It doesn't have any effect on other setups.

1.22.5

  • Headers won't be printed when calling yarn init with the -2 flag

    Maël Nison

  • Files with the .cjs extension will be spawned by yarnPath using `execPath

    #8144 - bgotink

  • Generates local yarn verions as .cjs files when calling yarn set version

    #8145 - bgotink

  • Sorts files when running yarn pack to produce identical layout on Windows and Unix systems

    #8142 - Merceyz

1.22.4 / 1.22.3

Those versions didn't contain any changes and were just triggered by our infra while working on the tests.

1.22.2

  • Ignores .yarnrc.yml by default when running yarn pack

... (truncated)

Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/traggo/server/network/alerts).
dependabot[bot] commented 2 years ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.