search

msonnberger / queued

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

Update all non-major dependencies #196

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
@lucia-auth/adapter-postgresql 1.0.0 -> 1.0.1 age adoption passing confidence
@lucia-auth/oauth 1.0.1 -> 1.1.0 age adoption passing confidence
@playwright/test (source) 1.33.0 -> 1.34.0 age adoption passing confidence
@sveltejs/kit (source) 1.17.0 -> 1.18.0 age adoption passing confidence
drizzle-kit 0.17.6 -> 0.18.0 age adoption passing confidence
drizzle-orm 0.25.4 -> 0.26.0 age adoption passing confidence
eslint (source) 8.40.0 -> 8.41.0 age adoption passing confidence
lucia-auth 1.5.0 -> 1.6.0 age adoption passing confidence
lucide-svelte (source) 0.217.0 -> 0.220.0 age adoption passing confidence
tslib (source) 2.5.0 -> 2.5.2 age adoption passing confidence
vite (source) 4.3.7 -> 4.3.8 age adoption passing confidence

Release Notes

Microsoft/playwright ### [`v1.34.0`](https://togithub.com/microsoft/playwright/releases/tag/v1.34.0) [Compare Source](https://togithub.com/Microsoft/playwright/compare/v1.33.0...v1.34.0) ##### Highlights - UI Mode now shows steps, fixtures and attachments: - New property [`testProject.teardown`](https://playwright.dev/docs/api/class-testproject#test-project-teardown) to specify a project that needs to run after this and all dependent projects have finished. Teardown is useful to cleanup any resources acquired by this project. A common pattern would be a `setup` dependency with a corresponding `teardown`: ```js // playwright.config.ts import { defineConfig } from '@​playwright/test'; export default defineConfig({ projects: [ { name: 'setup', testMatch: /global.setup\.ts/, teardown: 'teardown', }, { name: 'teardown', testMatch: /global.teardown\.ts/, }, { name: 'chromium', use: devices['Desktop Chrome'], dependencies: ['setup'], }, { name: 'firefox', use: devices['Desktop Firefox'], dependencies: ['setup'], }, { name: 'webkit', use: devices['Desktop Safari'], dependencies: ['setup'], }, ], }); ``` - New method [`expect.configure`](https://playwright.dev/docs/test-assertions#expectconfigure) to create pre-configured expect instance with its own defaults such as `timeout` and `soft`. ```js const slowExpect = expect.configure({ timeout: 10000 }); await slowExpect(locator).toHaveText('Submit'); // Always do soft assertions. const softExpect = expect.configure({ soft: true }); ``` - New options `stderr` and `stdout` in [`testConfig.webServer`](https://playwright.dev/docs/api/class-testconfig#test-config-web-server) to configure output handling: ```js // playwright.config.ts import { defineConfig } from '@​playwright/test'; export default defineConfig({ // Run your local dev server before starting the tests webServer: { command: 'npm run start', url: 'http://127.0.0.1:3000', reuseExistingServer: !process.env.CI, stdout: 'pipe', stderr: 'pipe', }, }); ``` - New [`locator.and()`](https://playwright.dev/docs/api/class-locator#locator-and) to create a locator that matches both locators. ```js const button = page.getByRole('button').and(page.getByTitle('Subscribe')); ``` - New events [`browserContext.on('console')`](https://playwright.dev/docs/api/class-browsercontext#browser-context-event-console) and [`browserContext.on('dialog')`](https://playwright.dev/docs/api/class-browsercontext#browser-context-event-dialog) to subscribe to any dialogs and console messages from any page from the given browser context. Use the new methods [`consoleMessage.page()`](https://playwright.dev/docs/api/class-consolemessage#console-message-page) and [`dialog.page()`](https://playwright.dev/docs/api/class-dialog#dialog-page) to pin-point event source. ##### ⚠️ Breaking changes - `npx playwright test` no longer works if you install both `playwright` and `@playwright/test`. There's no need to install both, since you can always import browser automation APIs from `@playwright/test` directly: ```js // automation.ts import { chromium, firefox, webkit } from '@​playwright/test'; /* ... */ ``` - Node.js 14 is no longer supported since it [reached its end-of-life](https://nodejs.dev/en/about/releases/) on April 30, 2023. ##### Browser Versions - Chromium 114.0.5735.26 - Mozilla Firefox 113.0 - WebKit 16.4 This version was also tested against the following stable channels: - Google Chrome 113 - Microsoft Edge 113
sveltejs/kit ### [`v1.18.0`](https://togithub.com/sveltejs/kit/blob/HEAD/packages/kit/CHANGELOG.md#​1180) [Compare Source](https://togithub.com/sveltejs/kit/compare/@sveltejs/kit@1.17.1...@sveltejs/kit@1.18.0) ##### Minor Changes - security: Stop implicitly tracking URLs as dependencies in server-side `load`s ([#​9945](https://togithub.com/sveltejs/kit/pull/9945)) ### [`v1.17.1`](https://togithub.com/sveltejs/kit/blob/HEAD/packages/kit/CHANGELOG.md#​1171) [Compare Source](https://togithub.com/sveltejs/kit/compare/@sveltejs/kit@1.17.0...@sveltejs/kit@1.17.1) ##### Patch Changes - fix: ensure styles are loaded in dev mode for routes containing special characters ([#​9894](https://togithub.com/sveltejs/kit/pull/9894)) - feat: warn users when enhancing forms with files but no `enctype="multipart/form-data"` ([#​9888](https://togithub.com/sveltejs/kit/pull/9888))
drizzle-team/drizzle-kit-mirror ### [`v0.18.0`](https://togithub.com/drizzle-team/drizzle-kit-mirror/releases/tag/v0.18.0): 0.18.0 [Compare Source](https://togithub.com/drizzle-team/drizzle-kit-mirror/compare/v0.17.6...v0.18.0) ### drizzle-kit@0.18.0 πŸŽ‰πŸŽ‰πŸŽ‰ #### New features πŸŽ‰ ##### New ways to define drizzle config file You can now specify the configuration not only in the `.json` format but also in `.ts` and `.js` formats.
**TypeScript example** ```ts import { Config } from "src"; export default { schema: "", connectionString: process.env.DB_URL, out: "", breakpoints: true } satisfies Config; ``` **JavaScript example** ```js /** @​type { import("drizzle-kit").Config } */ export default { schema: "", connectionString: "", out: "", breakpoints: true }; ``` #### New commands πŸŽ‰ ##### `drizzle-kit push:mysql` You can now push your MySQL schema directly to the database without the need to create and manage migration files. This feature proves to be particularly useful for rapid local development and when working with PlanetScale databases. By pushing the MySQL schema directly to the database, you can streamline the development process and avoid the overhead of managing migration files. This allows for more efficient iteration and quick deployment of schema changes during local development. ##### How to setup your codebase for drizzle-kit push feature? 1. For this feature, you need to create a `drizzle.config.[ts|js|json]` file. We recommend using `.ts` or `.js` files as they allow you to easily provide the database connection information as secret variables You'll need to specify `schema` and `connectionString`(or `db`, `port`, `host`, `password`, etc.) to make `drizzle-kit push:mysql` work `drizzle.config.ts` example ```ts copy import { Config } from "src"; export default { schema: "./schema.ts", connectionString: process.env.DB_URL, } satisfies Config; ``` 2. Run `drizzle-kit push:mysql` 3. If Drizzle detects any potential `data-loss` issues during a migration, it will prompt you to approve whether the data should be truncated or not in order to ensure a successful migration 4. Approve or reject the action that Drizzle needs to perform in order to push your schema changes to the database. 5. Done βœ…
drizzle-team/drizzle-orm ### [`v0.26.0`](https://togithub.com/drizzle-team/drizzle-orm/releases/tag/0.26.0) [Compare Source](https://togithub.com/drizzle-team/drizzle-orm/compare/0.25.4...0.26.0) ### Drizzle ORM 0.26.0 is here πŸŽ‰ #### README docs are fully tranferred to web The documentation has been completely reworked and updated with additional examples and explanations. You can find it here: https://orm.drizzle.team. Furthermore, the entire documentation has been made open source, allowing you to edit and add any information you deem important for the community. Visit https://github.com/drizzle-team/drizzle-orm-docs to access the open-sourced documentation. Additionally, you can create specific documentation issues in this repository #### New Features Introducing our first helper built on top of Drizzle Core API syntax: **the Relational Queries!** πŸŽ‰ With Drizzle RQ you can do: 1. Any amount of relations that will be mapped for you 2. Including or excluding! specific columns. You can also combine these options 3. Harness the flexibility of the `where` statements, allowing you to define custom conditions beyond the predefined ones available in the Drizzle Core API. 4. Expand the functionality by incorporating additional extras columns using SQL templates. For more examples, refer to the documentation. Most importantly, regardless of the size of your query, Drizzle will always generate a **SINGLE optimized query**. This efficiency extends to the usage of **Prepared Statements**, which are fully supported within the Relational Query Builder. For more info: [Prepared Statements in Relational Query Builder](https://orm.drizzle.team/rqb#prepared-statements) **Example of setting one-to-many relations** > As you can observe, `relations` are a distinct concept that coexists alongside the main Drizzle schema. You have the flexibility to opt-in or opt-out of them at any time without affecting the `drizzle-kit` migrations or the logic for Core API's types and runtime. ```ts import { integer, serial, text, pgTable } from 'drizzle-orm/pg-core'; import { relations } from 'drizzle-orm'; export const users = pgTable('users', { id: serial('id').primaryKey(), name: text('name').notNull(), }); export const usersConfig = relations(users, ({ many }) => ({ posts: many(posts), })); export const posts = pgTable('posts', { id: serial('id').primaryKey(), content: text('content').notNull(), authorId: integer('author_id').notNull(), }); export const postsConfig = relations(posts, ({ one }) => ({ author: one(users, { fields: [posts.authorId], references: [users.id] }), })); ``` **Example of querying you database** Step 1: Provide all tables and relations to `drizzle` function > `drizzle` import depends on the database driver you're using ```ts import * as schema from './schema'; import { drizzle } from 'drizzle-orm/...'; const db = drizzle(client, { schema }); await db.query.users.findMany(...); ``` If you have schema in multiple files ```ts import * as schema1 from './schema1'; import * as schema2 from './schema2'; import { drizzle } from 'drizzle-orm/...'; const db = drizzle(client, { schema: { ...schema1, ...schema2 } }); await db.query.users.findMany(...); ``` Step 2: Query your database with Relational Query Builder **Select all users** ```ts const users = await db.query.users.findMany(); ``` **Select first users** > `.findFirst()` will add limit 1 to the query ```ts const user = await db.query.users.findFirst(); ``` **Select all users** Get all posts with just `id`, `content` and include `comments` ```ts const posts = await db.query.posts.findMany({ columns: { id: true, content: true, }, with: { comments: true, } }); ``` **Select all posts excluding `content` column** ```ts const posts = await db.query.posts.findMany({ columns: { content: false, }, }); ``` For more examples you can check [full docs](https://orm.drizzle.team/rqb) for Relational Queries #### Bug fixes - πŸ› Fixed partial joins with prefixed tables ([#​542](https://togithub.com/drizzle-team/drizzle-orm/issues/542)) #### Drizzle Kit updates ##### New ways to define drizzle config file You can now specify the configuration not only in the `.json` format but also in `.ts` and `.js` formats.
**TypeScript example** ```ts import { Config } from "drizzle-kit"; export default { schema: "", connectionString: process.env.DB_URL, out: "", breakpoints: true } satisfies Config; ``` **JavaScript example** ```js /** @​type { import("drizzle-kit").Config } */ export default { schema: "", connectionString: "", out: "", breakpoints: true }; ``` #### New commands πŸŽ‰ ##### `drizzle-kit push:mysql` You can now push your MySQL schema directly to the database without the need to create and manage migration files. This feature proves to be particularly useful for rapid local development and when working with PlanetScale databases. By pushing the MySQL schema directly to the database, you can streamline the development process and avoid the overhead of managing migration files. This allows for more efficient iteration and quick deployment of schema changes during local development. ##### How to setup your codebase for drizzle-kit push feature? 1. For this feature, you need to create a `drizzle.config.[ts|js|json]` file. We recommend using `.ts` or `.js` files as they allow you to easily provide the database connection information as secret variables You'll need to specify `schema` and `connectionString`(or `db`, `port`, `host`, `password`, etc.) to make `drizzle-kit push:mysql` work `drizzle.config.ts` example ```ts copy import { Config } from "src"; export default { schema: "./schema.ts", connectionString: process.env.DB_URL, } satisfies Config; ``` 2. Run `drizzle-kit push:mysql` 3. If Drizzle detects any potential `data-loss` issues during a migration, it will prompt you to approve whether the data should be truncated or not in order to ensure a successful migration 4. Approve or reject the action that Drizzle needs to perform in order to push your schema changes to the database. 5. Done βœ…
eslint/eslint ### [`v8.41.0`](https://togithub.com/eslint/eslint/releases/tag/v8.41.0) [Compare Source](https://togithub.com/eslint/eslint/compare/v8.40.0...v8.41.0) #### Features - [`880a431`](https://togithub.com/eslint/eslint/commit/880a4317b949e575a4a6c5e8baaba1eea7674cc6) feat: change default ignore pattern to `**/node_modules/` in flat config ([#​17184](https://togithub.com/eslint/eslint/issues/17184)) (Milos Djermanovic) - [`8bf5505`](https://togithub.com/eslint/eslint/commit/8bf550594fca6d29fab1a3453e701c1a457767e1) feat: expose `shouldUseFlatConfig` ([#​17169](https://togithub.com/eslint/eslint/issues/17169)) (Connor Prussin) #### Bug Fixes - [`4f5440d`](https://togithub.com/eslint/eslint/commit/4f5440db631707b17140c4e5cc7beb223afbd2b9) fix: incorrect warning message for ignored dotfiles ([#​17196](https://togithub.com/eslint/eslint/issues/17196)) (Milos Djermanovic) - [`94da96c`](https://togithub.com/eslint/eslint/commit/94da96cbf0fb2bb6694fa2e757eb1b3e74c40db7) fix: unify `LintMessage` type ([#​17076](https://togithub.com/eslint/eslint/issues/17076)) (Brandon Mills) - [`0c415cd`](https://togithub.com/eslint/eslint/commit/0c415cda5d76dbe5120ab9f3c4c81320538e35f0) fix: validate `ignorePatterns` constructor option in `FlatESLint` class ([#​17139](https://togithub.com/eslint/eslint/issues/17139)) (Milos Djermanovic) - [`9682d66`](https://togithub.com/eslint/eslint/commit/9682d669e4ee8641293914e21679f40fee8bc354) fix: switch `grapheme-splitter` to `graphemer` ([#​17160](https://togithub.com/eslint/eslint/issues/17160)) (fisker Cheung) #### Documentation - [`7709b14`](https://togithub.com/eslint/eslint/commit/7709b14e18ad4e11c1119ed6575454243b8e7084) docs: Update README (GitHub Actions Bot) - [`7f183e0`](https://togithub.com/eslint/eslint/commit/7f183e020579380fa57473caaf9ed154470c25b3) docs: Update triage process description ([#​17157](https://togithub.com/eslint/eslint/issues/17157)) (Nicholas C. Zakas) - [`b68346b`](https://togithub.com/eslint/eslint/commit/b68346b290d55324e73868ca42b3854157b27375) docs: fix license to reflect relicensing of jshint ([#​17165](https://togithub.com/eslint/eslint/issues/17165)) (Stefan Bischof) #### Chores - [`f43216a`](https://togithub.com/eslint/eslint/commit/f43216a8c77ab6cf1d0823978e8c728786b4cba7) chore: upgrade [@​eslint/js](https://togithub.com/eslint/js)[@​8](https://togithub.com/8).41.0 ([#​17200](https://togithub.com/eslint/eslint/issues/17200)) (Milos Djermanovic) - [`95c3007`](https://togithub.com/eslint/eslint/commit/95c300780a1cfd9ad680bc78850542eb55d7fbf4) chore: package.json update for [@​eslint/js](https://togithub.com/eslint/js) release (ESLint Jenkins) - [`ddc5291`](https://togithub.com/eslint/eslint/commit/ddc5291debd90ff476e17c532af7577e26720b91) chore: don't use deprecated `context` methods in `ast-utils` tests ([#​17194](https://togithub.com/eslint/eslint/issues/17194)) (Milos Djermanovic) - [`b1516db`](https://togithub.com/eslint/eslint/commit/b1516db51514032ed06e1425c4b1f955238dc682) chore: Fix return type of `findFlatConfigFile` ([#​17161](https://togithub.com/eslint/eslint/issues/17161)) (Milos Djermanovic) - [`918b0fd`](https://togithub.com/eslint/eslint/commit/918b0fd21723e84bd7acb17942a36606f1d8360a) perf: Store indent descriptors in a plain array ([#​17148](https://togithub.com/eslint/eslint/issues/17148)) (Francesco Trotta) - [`4caa344`](https://togithub.com/eslint/eslint/commit/4caa34449555d8a680222ec2049d97c59476c11e) refactor: locateConfigFileToUse returns an Error object ([#​17159](https://togithub.com/eslint/eslint/issues/17159)) (ε”―η„Ά)
pilcrowOnPaper/lucia ### [`v1.6.0`](https://togithub.com/pilcrowOnPaper/lucia/blob/HEAD/packages/lucia-auth/CHANGELOG.md#​160) ##### Minor changes - [#​626](https://togithub.com/pilcrowOnPaper/lucia/pull/626) by [@​pilcrowOnPaper](https://togithub.com/pilcrowOnPaper) : `web()` middleware can take `Headers` or `Response` - [#​626](https://togithub.com/pilcrowOnPaper/lucia/pull/626) by [@​pilcrowOnPaper](https://togithub.com/pilcrowOnPaper) : Add `nextjs()` middleware ##### Patch changes - [#​626](https://togithub.com/pilcrowOnPaper/lucia/pull/626) by [@​pilcrowOnPaper](https://togithub.com/pilcrowOnPaper) : Fix Express middleware returning broken url
lucide-icons/lucide ### [`v0.220.0`](https://togithub.com/lucide-icons/lucide/releases/tag/v0.220.0): New icons v0.220.0 [Compare Source](https://togithub.com/lucide-icons/lucide/compare/v0.219.0...v0.220.0) > @​ generate:changelog /home/runner/work/lucide/lucide > node ./scripts/generateChangelog.mjs "--old-tag=v0.219.0" #### Modified Icons πŸ”¨ - `diamond` ([#​1294](https://togithub.com/lucide-icons/lucide/issues/1294)) by [@​jguddas](https://togithub.com/jguddas) ### [`v0.219.0`](https://togithub.com/lucide-icons/lucide/releases/tag/v0.219.0): New icons v0.219.0 [Compare Source](https://togithub.com/lucide-icons/lucide/compare/v0.218.0...v0.219.0) > @​ generate:changelog /home/runner/work/lucide/lucide > node ./scripts/generateChangelog.mjs "--old-tag=v0.218.0" #### New icons 🎨 - `sparkle` ([#​1220](https://togithub.com/lucide-icons/lucide/issues/1220)) by [@​Shiva953](https://togithub.com/Shiva953) ### [`v0.218.0`](https://togithub.com/lucide-icons/lucide/releases/tag/v0.218.0): New icons v0.218.0 [Compare Source](https://togithub.com/lucide-icons/lucide/compare/v0.217.0...v0.218.0) > @​ generate:changelog /home/runner/work/lucide/lucide > node ./scripts/generateChangelog.mjs "--old-tag=v0.217.0" #### Modified Icons πŸ”¨ - `life-buoy` ([#​1279](https://togithub.com/lucide-icons/lucide/issues/1279)) by [@​danielbayley](https://togithub.com/danielbayley)
Microsoft/tslib ### [`v2.5.2`](https://togithub.com/microsoft/tslib/releases/tag/2.5.2): tslib 2.5.2 [Compare Source](https://togithub.com/Microsoft/tslib/compare/2.5.1...2.5.2) This release [explicitly re-exports helpers](https://togithub.com/microsoft/tslib/pull/204) to work around TypeScript's incomplete symbol resolution for tslib. ### [`v2.5.1`](https://togithub.com/microsoft/tslib/releases/tag/2.5.1): tslib 2.5.1 [Compare Source](https://togithub.com/Microsoft/tslib/compare/2.5.0...2.5.1) This release of tslib provides fixes for two issues. First, [it reverses the order of `init` hooks provided by decorators](https://togithub.com/microsoft/tslib/pull/202) to correctly reflect proposed behavior. Second, it [corrects the `exports` field of tslib's `package.json` and provides accurate declaration files](https://togithub.com/microsoft/tslib/pull/202) so that it may be consumed under the `node16` and `bundler` settings for `moduleResolution.`
vitejs/vite ### [`v4.3.8`](https://togithub.com/vitejs/vite/blob/HEAD/packages/vite/CHANGELOG.md#small438-2023-05-18-small) [Compare Source](https://togithub.com/vitejs/vite/compare/v4.3.7...v4.3.8) - fix: avoid outdated module to crash in importAnalysis after restart ([#​13231](https://togithub.com/vitejs/vite/issues/13231)) ([3609e79](https://togithub.com/vitejs/vite/commit/3609e79)), closes [#​13231](https://togithub.com/vitejs/vite/issues/13231) - fix(ssr): skip updateCjsSsrExternals if legacy flag disabled ([#​13230](https://togithub.com/vitejs/vite/issues/13230)) ([13fc345](https://togithub.com/vitejs/vite/commit/13fc345)), closes [#​13230](https://togithub.com/vitejs/vite/issues/13230)

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 May 20, 2023 3:02am