msonnberger / queued

https://queued.vercel.app
3 stars 0 forks source link

Update all non-major dependencies #221

Closed renovate[bot] closed 1 year ago

renovate[bot] commented 1 year ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@ianvs/prettier-plugin-sort-imports 4.0.2 -> 4.1.0 age adoption passing confidence
@playwright/test (source) 1.36.0 -> 1.36.1 age adoption passing confidence
drizzle-kit 0.19.5 -> 0.19.6 age adoption passing confidence
eslint (source) 8.44.0 -> 8.45.0 age adoption passing confidence
prettier-plugin-tailwindcss 0.4.0 -> 0.4.1 age adoption passing confidence
svelte-headlessui (source) 0.0.19 -> 0.0.20 age adoption passing confidence
tailwind-merge 1.13.2 -> 1.14.0 age adoption passing confidence

Release Notes

ianvs/prettier-plugin-sort-imports (@​ianvs/prettier-plugin-sort-imports) ### [`v4.1.0`](https://togithub.com/IanVS/prettier-plugin-sort-imports/releases/tag/v4.1.0) [Compare Source](https://togithub.com/ianvs/prettier-plugin-sort-imports/compare/v4.0.2...v4.1.0) #### What's Changed - Add Prettier v3 to Peer dependencies by [@​Sparticuz](https://togithub.com/Sparticuz) in [https://github.com/IanVS/prettier-plugin-sort-imports/pull/111](https://togithub.com/IanVS/prettier-plugin-sort-imports/pull/111) - Upgrade to Prettier 3 in devDependencies by [@​fbartho](https://togithub.com/fbartho) in [https://github.com/IanVS/prettier-plugin-sort-imports/pull/75](https://togithub.com/IanVS/prettier-plugin-sort-imports/pull/75) #### New Contributors - [@​Sparticuz](https://togithub.com/Sparticuz) made their first contribution in [https://github.com/IanVS/prettier-plugin-sort-imports/pull/111](https://togithub.com/IanVS/prettier-plugin-sort-imports/pull/111) **Full Changelog**: https://github.com/IanVS/prettier-plugin-sort-imports/compare/v4.0.2...v4.1.0
Microsoft/playwright (@​playwright/test) ### [`v1.36.1`](https://togithub.com/microsoft/playwright/releases/tag/v1.36.1) [Compare Source](https://togithub.com/Microsoft/playwright/compare/v1.36.0...v1.36.1) ##### Highlights [https://github.com/microsoft/playwright/issues/24184](https://togithub.com/microsoft/playwright/issues/24184) - \[REGRESSION]: Snapshot name contains some random string after test name when tests are run in container ##### Browser Versions - Chromium 115.0.5790.75 - Mozilla Firefox 115.0 - WebKit 17.0 This version was also tested against the following stable channels: - Google Chrome 114 - Microsoft Edge 114
drizzle-team/drizzle-kit-mirror (drizzle-kit) ### [`v0.19.6`](https://togithub.com/drizzle-team/drizzle-kit-mirror/releases/tag/v0.19.6): 0.19.6 [Compare Source](https://togithub.com/drizzle-team/drizzle-kit-mirror/compare/v0.19.5...v0.19.6) - 🐛 [Impossible to push schema changes due to ER_DROP_INDEX_FK](https://togithub.com/drizzle-team/drizzle-kit-mirror/issues/124) n this issue, there were two problems with MySQL migration generation and schema pushing: 1. MySQL, like SQLite, does not have a difference in unique constraints and unique indexes at the database level. This aspect was handled correctly for SQLite but not for MySQL. In MySQL, when a `unique index` is created from a Drizzle schema, it is stored as both a unique constraint and a unique index in the database. Therefore, there was no distinction between the two. This led to incorrect assumptions during schema pushes regarding the creation, dropping, or storage of unique indexes. In the current fixes, Drizzle Kit now treats unique constraints as unique indexes for MySQL and SQLite only. 2. Drizzle Kit was attempting to drop the primary key when it shouldn't have done so. The issue was with incorrect querying of the information schema. Drizzle Kit was examining the column definition and the `column_key` setting from the `information_schema.columns table`. However, it turns out that the `column_key` value can indicate `PRIMARY` even for columns that are both `UNIQUE` and `NOT_NULL`. Which is correct in database terms, but not valid in the determination if this constraint was created as Primary Key. I have made changes to address this problem by utilizing the `information_schema.table_constraints` table, which provides a proper distinction between primary keys and columns with the combination of `UNIQUE` and `NOT_NULL` - ✍️ Added new collision check between the same names in unique indexes and unique constraints in schema(for MySQL)
eslint/eslint (eslint) ### [`v8.45.0`](https://togithub.com/eslint/eslint/releases/tag/v8.45.0) [Compare Source](https://togithub.com/eslint/eslint/compare/v8.44.0...v8.45.0) #### Features - [`cdd063c`](https://togithub.com/eslint/eslint/commit/cdd063c388bbfe1781d7a864a832f03a2c1cc277) feat: Expose LegacyESLint in unsupported API ([#​17341](https://togithub.com/eslint/eslint/issues/17341)) (Nicholas C. Zakas) - [`d34abe5`](https://togithub.com/eslint/eslint/commit/d34abe59eb23932dcbc79757d7932d08ee8b20e5) feat: fix indent rule for else-if ([#​17318](https://togithub.com/eslint/eslint/issues/17318)) (Milos Djermanovic) #### Bug Fixes - [`b79b6fb`](https://togithub.com/eslint/eslint/commit/b79b6fb64473969b426d086b484d2e29594a5e9a) fix: Fix suggestion message in `no-useless-escape` ([#​17339](https://togithub.com/eslint/eslint/issues/17339)) (Francesco Trotta) - [`c667055`](https://togithub.com/eslint/eslint/commit/c667055fb9da8ebac3a99f6e5a8b5565cc86af8e) fix: provide unique `fix` and `fix.range` objects in lint messages ([#​17332](https://togithub.com/eslint/eslint/issues/17332)) (Milos Djermanovic) #### Documentation - [`89f3225`](https://togithub.com/eslint/eslint/commit/89f3225108c66425e4132f76db6c1ab13aac98d7) docs: add playground links to correct and incorrect code blocks ([#​17306](https://togithub.com/eslint/eslint/issues/17306)) (Josh Goldberg ✨) - [`f8892b5`](https://togithub.com/eslint/eslint/commit/f8892b52920b8967f9e7bec23c75b74e03977d6b) docs: Expand rule option schema docs ([#​17198](https://togithub.com/eslint/eslint/issues/17198)) (Matt Wilkinson) - [`8bcbf11`](https://togithub.com/eslint/eslint/commit/8bcbf11b6050418262ffa8e0ca37f365ae92e7ce) docs: Config Migration Guide ([#​17230](https://togithub.com/eslint/eslint/issues/17230)) (Ben Perlmutter) - [`bb30908`](https://togithub.com/eslint/eslint/commit/bb3090897166dbfd2931a43a70e2a5c1f3fa0a07) docs: Update README (GitHub Actions Bot) - [`84d243b`](https://togithub.com/eslint/eslint/commit/84d243b245b01b667f0752b592e8bda02a9aa2b1) docs: Update README (GitHub Actions Bot) - [`b762632`](https://togithub.com/eslint/eslint/commit/b762632298f20c4f81e7d01ab850c3f5e3874637) docs: Update README (GitHub Actions Bot) - [`138c096`](https://togithub.com/eslint/eslint/commit/138c096bc9468b553dbafc0e573c6522a17a7922) docs: add more prefer-destructuring examples with array destructuring ([#​17330](https://togithub.com/eslint/eslint/issues/17330)) (Milos Djermanovic) - [`1fc50a8`](https://togithub.com/eslint/eslint/commit/1fc50a89753346f4f4c786ffd20ac4cf185bb036) docs: `max-len` rule `code` and `tabWidth` as positional arguments ([#​17331](https://togithub.com/eslint/eslint/issues/17331)) (Jesús Leganés-Combarro) #### Chores - [`68f63d7`](https://togithub.com/eslint/eslint/commit/68f63d76ce785fab4f42b76f1599026eea379bf7) chore: package.json update for [@​eslint/js](https://togithub.com/eslint/js) release (ESLint Jenkins) - [`5ca9b4d`](https://togithub.com/eslint/eslint/commit/5ca9b4d29f747e9cf5c9055e85c93b3b605d57fc) chore: update eslint-config-eslint exports ([#​17336](https://togithub.com/eslint/eslint/issues/17336)) (Milos Djermanovic) - [`7bf2e86`](https://togithub.com/eslint/eslint/commit/7bf2e86022c9e95db4ca1472fddfa2ea4edd1870) chore: remove unused dependencies ([#​17352](https://togithub.com/eslint/eslint/issues/17352)) (Percy Ma) - [`c6f8cd0`](https://togithub.com/eslint/eslint/commit/c6f8cd0d62e4a3c314c6860ff367490bbd05325a) chore: Remove `defaultIgnores` from FlatESLint private members ([#​17349](https://togithub.com/eslint/eslint/issues/17349)) (Francesco Trotta) - [`0052374`](https://togithub.com/eslint/eslint/commit/0052374035672efe9129343fc00ee51a4c288ff3) chore: move jsdoc settings to eslint-config-eslint ([#​17338](https://togithub.com/eslint/eslint/issues/17338)) (唯然)
tailwindlabs/prettier-plugin-tailwindcss (prettier-plugin-tailwindcss) ### [`v0.4.1`](https://togithub.com/tailwindlabs/prettier-plugin-tailwindcss/blob/HEAD/CHANGELOG.md#041---2023-07-14) [Compare Source](https://togithub.com/tailwindlabs/prettier-plugin-tailwindcss/compare/v0.4.0...v0.4.1) ##### Fixed - Don't move partial classes inside Twig attributes ([#​184](https://togithub.com/tailwindlabs/prettier-plugin-tailwindcss/pull/184))
dcastil/tailwind-merge (tailwind-merge) ### [`v1.14.0`](https://togithub.com/dcastil/tailwind-merge/releases/tag/v1.14.0) [Compare Source](https://togithub.com/dcastil/tailwind-merge/compare/v1.13.2...v1.14.0) ##### New Features - Improve support for arbitrary values by [@​dcastil](https://togithub.com/dcastil) in [https://github.com/dcastil/tailwind-merge/pull/263](https://togithub.com/dcastil/tailwind-merge/pull/263) - Previously, tailwind-merge checked the content of the arbitrary value portion of a class in most cases to understand whether the type of the arbitrary value is correct (e.g. it checked for number followed by length unit for the length type). That lead to the issue that a class like `mt-[calc(theme(fontSize.4xl)/1.125)]` would not be recognized correctly because no length unit is present in the arbitrary value. - I changed the check of the arbitrary value to also pass when a `calc()`, `min()`, `max()` and `clamp()` function is used in the arbitrary value. - In ambiguous cases, you can use data type labels to mark the type of a class. [Read more](https://togithub.com/dcastil/tailwind-merge/blob/v1.14.0/docs/features.md#supports-arbitrary-values) - Moreover, I removed the check where the type of the arbitrary value is unambiguous. In the class `mt-[…]` the arbitrary value can only be a length, so I don't check for it. A consequence of this is that if you use non-Tailwind classes like `mt-[this-is-totally-not-tailwind]`, tailwind-merge will recognize it as a Tailwind class from now on. **Please don't use classes that look like Tailwind classes with arbitrary value but aren't Tailwind classes with tailwind-merge (in default config) to prevent incorrect merging behavior**. ##### Bug Fixes - Fix `col-span-full` class missing in default config by [@​dcastil](https://togithub.com/dcastil) in [https://github.com/dcastil/tailwind-merge/pull/267](https://togithub.com/dcastil/tailwind-merge/pull/267) - Fix arbitrary value with no present length unit not being recognized by [@​dcastil](https://togithub.com/dcastil) in [https://github.com/dcastil/tailwind-merge/pull/263](https://togithub.com/dcastil/tailwind-merge/pull/263) ##### Documentation - Add missing info about where to call config functions to docs by [@​dcastil](https://togithub.com/dcastil) in [https://github.com/dcastil/tailwind-merge/pull/264](https://togithub.com/dcastil/tailwind-merge/pull/264) **Full Changelog**: https://github.com/dcastil/tailwind-merge/compare/v1.13.2...v1.14.0

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.



This PR has been generated by Mend Renovate. View repository job log here.

vercel[bot] commented 1 year ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
queued ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 16, 2023 8:12pm