vercel[bot]
commented
12 months ago The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| programming-in-th | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Sep 17, 2023 9:10pm |
github-actions[bot]
This PR contains the following updates:
3.409.0->3.414.03.409.0->3.414.06.18.0->6.19.01.37.1->1.38.05.2.0->5.3.18.9.8->8.10.018.17.15->18.17.176.6.0->6.7.06.6.0->6.7.08.7.4->8.7.65.2.0->5.3.11.66.1->1.67.0Release Notes
aws/aws-sdk-js-v3 (@aws-sdk/client-s3)
### [`v3.414.0`](https://togithub.com/aws/aws-sdk-js-v3/blob/HEAD/clients/client-s3/CHANGELOG.md#34140-2023-09-15) [Compare Source](https://togithub.com/aws/aws-sdk-js-v3/compare/v3.413.0...v3.414.0) ##### Features - **region-config:** add aws region runtime extension codegen ([#5157](https://togithub.com/aws/aws-sdk-js-v3/issues/5157)) ([b9d59e8](https://togithub.com/aws/aws-sdk-js-v3/commit/b9d59e81696f9628c6502473bb01a2d1a617e928)) ### [`v3.413.0`](https://togithub.com/aws/aws-sdk-js-v3/blob/HEAD/clients/client-s3/CHANGELOG.md#34130-2023-09-14) **Note:** Version bump only for package [@aws-sdk/client-s3](https://togithub.com/aws-sdk/client-s3) ### [`v3.412.0`](https://togithub.com/aws/aws-sdk-js-v3/blob/HEAD/clients/client-s3/CHANGELOG.md#34120-2023-09-13) [Compare Source](https://togithub.com/aws/aws-sdk-js-v3/compare/v3.410.0...v3.412.0) **Note:** Version bump only for package [@aws-sdk/client-s3](https://togithub.com/aws-sdk/client-s3) ### [`v3.410.0`](https://togithub.com/aws/aws-sdk-js-v3/blob/HEAD/clients/client-s3/CHANGELOG.md#34100-2023-09-11) [Compare Source](https://togithub.com/aws/aws-sdk-js-v3/compare/v3.409.0...v3.410.0) **Note:** Version bump only for package [@aws-sdk/client-s3](https://togithub.com/aws-sdk/client-s3)aws/aws-sdk-js-v3 (@aws-sdk/s3-request-presigner)
### [`v3.414.0`](https://togithub.com/aws/aws-sdk-js-v3/blob/HEAD/packages/s3-request-presigner/CHANGELOG.md#34140-2023-09-15) **Note:** Version bump only for package [@aws-sdk/s3-request-presigner](https://togithub.com/aws-sdk/s3-request-presigner) ### [`v3.413.0`](https://togithub.com/aws/aws-sdk-js-v3/blob/HEAD/packages/s3-request-presigner/CHANGELOG.md#34130-2023-09-14) **Note:** Version bump only for package [@aws-sdk/s3-request-presigner](https://togithub.com/aws-sdk/s3-request-presigner) ### [`v3.412.0`](https://togithub.com/aws/aws-sdk-js-v3/blob/HEAD/packages/s3-request-presigner/CHANGELOG.md#34120-2023-09-13) **Note:** Version bump only for package [@aws-sdk/s3-request-presigner](https://togithub.com/aws-sdk/s3-request-presigner) ### [`v3.410.0`](https://togithub.com/aws/aws-sdk-js-v3/blob/HEAD/packages/s3-request-presigner/CHANGELOG.md#34100-2023-09-11) **Note:** Version bump only for package [@aws-sdk/s3-request-presigner](https://togithub.com/aws-sdk/s3-request-presigner)codemirror/view (@codemirror/view)
### [`v6.19.0`](https://togithub.com/codemirror/view/blob/HEAD/CHANGELOG.md#6190-2023-09-14) [Compare Source](https://togithub.com/codemirror/view/compare/6.18.1...6.19.0) ##### Bug fixes Make sure the drop cursor is properly cleaned up even when another extension handles the drop event. Fix a crash related to non-inclusive replacing block decorations. ##### New features The new `EditorView.domEventObservers` (and the corresponding option to view plugins) allows you to register functions that are always called for an event, regardless of whether other handlers handled it. ### [`v6.18.1`](https://togithub.com/codemirror/view/blob/HEAD/CHANGELOG.md#6181-2023-09-11) [Compare Source](https://togithub.com/codemirror/view/compare/6.18.0...6.18.1) ##### Bug fixes Fix an issue where the editor duplicated text when the browser moved content into the focused text node on composition. Make sure `widgetMarker` is called for gutters on lines covered by a block replace decoration. Fix an issue where the cursor could be shown in a position that doesn't allow a cursor when the selection is in a block widget.Microsoft/playwright (@playwright/test)
### [`v1.38.0`](https://togithub.com/microsoft/playwright/releases/tag/v1.38.0) [Compare Source](https://togithub.com/Microsoft/playwright/compare/v1.37.1...v1.38.0) ##### UI Mode Updates  1. Zoom into time range. 2. Network panel redesign. ##### New APIs - [`browserContext.on('weberror')`][browserContext.on('weberror')] - [`locator.pressSequentially()`][locator.pressSequentially()] - The [`reporter.onEnd()`][reporter.onEnd()] now reports `startTime` and total run `duration`. ##### Deprecations - The following methods were deprecated: [`page.type()`][page.type()], [`frame.type()`][frame.type()], [`locator.type()`][locator.type()] and [`elementHandle.type()`][elementHandle.type()]. Please use [`locator.fill()`][locator.fill()] instead which is much faster. Use [`locator.pressSequentially()`][locator.pressSequentially()] only if there is a special keyboard handling on the page, and you need to press keys one-by-one. ##### Breaking Changes: Playwright no longer downloads browsers automatically > \[!NOTE] > If you are using `@playwright/test` package, this change **does not** affect you. Playwright recommends to use `@playwright/test` package and download browsers via `npx playwright install` command. If you are following this recommendation, nothing has changed for you. However, up to v1.38, installing the `playwright` package instead of `@playwright/test` did automatically download browsers. This is no longer the case, and we recommend to explicitly download browsers via `npx playwright install` command. **v1.37 and earlier** `playwright` package was downloading browsers during `npm install`, while `@playwright/test` was not. **v1.38 and later** `playwright` and `@playwright/test` packages do not download browsers during `npm install`. **Recommended migration** Run `npx playwright install` to download browsers after `npm install`. For example, in your CI configuration: ```yml - run: npm ci - run: npx playwright install --with-deps ``` **Alternative migration option - not recommended** Add `@playwright/browser-chromium`, `@playwright/browser-firefox` and `@playwright/browser-webkit` as a dependency. These packages download respective browsers during `npm install`. Make sure you keep the version of all playwright packages in sync: ```json5 // package.json { "devDependencies": { "playwright": "1.38.0", "@playwright/browser-chromium": "1.38.0", "@playwright/browser-firefox": "1.38.0", "@playwright/browser-webkit": "1.38.0" } } ``` ##### Browser Versions - Chromium 117.0.5938.62 - Mozilla Firefox 117.0 - WebKit 17.0 This version was also tested against the following stable channels: - Google Chrome 116 - Microsoft Edge 116 [`browserContext.on('weberror')`]: https://playwright.dev/docs/api/class-browsercontext#browser-context-event-web-error [`locator.pressSequentially()`]: https://playwright.dev/docs/api/class-locator#locator-press-sequentially [`reporter.onEnd()`]: https://playwright.dev/docs/api/class-reporter#reporter-on-end [`page.type()`]: https://playwright.dev/docs/api/class-page#page-type [`frame.type()`]: https://playwright.dev/docs/api/class-frame#frame-type [`locator.type()`]: https://playwright.dev/docs/api/class-locator#locator-type [`elementHandle.type()`]: https://playwright.dev/docs/api/class-elementhandle#element-handle-type [`locator.fill()`]: https://playwright.dev/docs/api/class-locator#locator-fill [`expect(value).toMatchSnapshot()`]: https://playwright.dev/docs/api/class-snapshotassertions#snapshot-assertions-to-match-snapshot-1 [`expect(page).toHaveScreenshot()`]: https://playwright.dev/docs/api/class-pageassertions#page-assertions-to-have-screenshot-1 [`expect(locator).toHaveScreenshot()`]: https://playwright.dev/docs/api/class-locatorassertions#locator-assertions-to-have-screenshot-1prisma/prisma (@prisma/client)
### [`v5.3.1`](https://togithub.com/prisma/prisma/releases/tag/5.3.1) [Compare Source](https://togithub.com/prisma/prisma/compare/5.3.0...5.3.1) Today, we are issuing the `5.3.1` patch release. ##### Fix in Prisma Client - [Duplicated keys in `metrics` properties](https://togithub.com/prisma/prisma/issues/21069) ### [`v5.3.0`](https://togithub.com/prisma/prisma/releases/tag/5.3.0) [Compare Source](https://togithub.com/prisma/prisma/compare/5.2.0...5.3.0) 🌟 **Help us spread the word about Prisma by starring the repo or [tweeting](https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20@prisma%20release%20v5.3.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/5.3.0) about the release.** 🌟 ### Highlights In this sprint, we’ve made bug fixes and overall improvements to Prisma Client. We’ve been working on a few projects that will be announced soon. Stay tuned for the upcoming releases for updates! #### Improvements and bug fixes We made the following changes: ##### Prisma Client improvements - Validation for `undefined` values in arrays in `Json` fields We added runtime validation for `undefined` values in arrays in `Json` fields. Prisma Client will now return an error when an array contains an `undefined` value. Therefore, we encourage you to add validation that either removes the value or transforms it to `null` if you stumble on the runtime validation: ```ts // Query await prisma.user.findMany({ where: { // JSON field preferences: [undefined, '"theme": "dark"', null, ] } }) // Example error message on running the query Can not use `undefined` value within array. Use `null` or filter out `undefined` values ``` - Performance improvements for models with many unique fields This release improves Prisma Client’s memory consumption for models with many `@unique` constraints. This was a regression from version 4.10.1, where in some cases, if a model had many unique constraints, Prisma Client would use up a lot of available memory. - Fixed the segmentation fault error that used to occur on ARM64 Linux binary targets - Metrics Preview feature improvements: - We updated the counters and gauge properties - We fixed the bug that caused the `prisma_pool_connections_open` metric to have a negative value in some cases. ##### Prisma Migrate improvements - Fixed an introspection bug for MongoDB views. Previously, if a MongoDB database contained a view, `prisma db pull` would throw an error. We resolved this, and views are now ignored. - Added the `PRISMA_SCHEMA_DISABLE_ADVISORY_LOCK` environment variable that enables you to disable [advisory locking](https://www.prisma.io/docs/concepts/components/prisma-migrate/migrate-development-production#advisory-locking). ##### [VS Code extension](https://marketplace.visualstudio.com/items?itemName=Prisma.prisma) improvements - Added support for rendering multi-line comments in tooltips when hovering on a block. - Improved the auto-completion for composite types in other blocks. - Added a Code Action that allows you to replace `SetDefault` with `NoAction` when using MySQL and the default/`foreignKeys` relation mode. #### Fixes and improvements ##### Prisma Migrate - [Percona-XtraDB-Cluster prohibits use of GET_LOCK with pxc_strict_mode = ENFORCING](https://togithub.com/prisma/prisma/issues/16020) - [MongoDB views should be ignored introspecting the database](https://togithub.com/prisma/prisma/issues/16179) - [Error in Connector on MongoDB executing listIndex: "system.views"](https://togithub.com/prisma/prisma/issues/17006) - [`prisma migrate deploy`: `MariaDB doesn't yet support 'GET_LOCK in cluster (WSREP_ON=ON)'`](https://togithub.com/prisma/prisma/issues/19350) ##### Prisma Client - [Remove all special cases for Data Proxy in our tests](https://togithub.com/prisma/prisma/issues/16101) - [Segmentation fault on ARM64 Linux](https://togithub.com/prisma/prisma/issues/18510) - [In the metrics feature a gauge & counter are swapped](https://togithub.com/prisma/prisma/issues/18760) - [The prisma metrics `prisma_pool_connections_open` has a bug where it goes negative](https://togithub.com/prisma/prisma/issues/18761) - [Prisma crashes with GraphQL queries of nested one-to-many relationship](https://togithub.com/prisma/prisma/issues/18787) - [P1017 Server has closed the connection on linux_arm64](https://togithub.com/prisma/prisma/issues/19209) - [`Error: socket hang up` on Linux/arm64](https://togithub.com/prisma/prisma/issues/19419) - [Panic in Query Engine with SIGABRT signal (Debian Bookworm, engineType = binary)](https://togithub.com/prisma/prisma/issues/19743) - [Prisma 5 drops `undefined` from Arrays when using Json fields with Postgres](https://togithub.com/prisma/prisma/issues/20325) - [Suspected memory leak in Lambda function after upgrading from 4.10.1](https://togithub.com/prisma/prisma/issues/20799) - [Error when generating - No unsupported field should reach that path](https://togithub.com/prisma/prisma/issues/20986) ##### Language tools (e.g. VS Code) - [Models with multi line comments only show last line in tooltip](https://togithub.com/prisma/language-tools/issues/861) - [Add VS Code quick fix / code action to replace `SetDefault` with `NoAction` when `provider = "mysql"` and `relationMode = "foreignKeys" | default`](https://togithub.com/prisma/language-tools/issues/1286) - [Composite Types aren't offered as being auto-completable in other blocks](https://togithub.com/prisma/language-tools/issues/1495) #### Credits Huge thanks to [@alencardc](https://togithub.com/alencardc), [@Oreilles](https://togithub.com/Oreilles), [@christianledgard](https://togithub.com/christianledgard), [@skyzh](https://togithub.com/skyzh), [@alula](https://togithub.com/alula), [@michaelpoellath](https://togithub.com/michaelpoellath), [@RobertCraigie](https://togithub.com/RobertCraigie), [@stephenwade](https://togithub.com/stephenwade) for helping!tanstack/table (@tanstack/react-table)
### [`v8.10.0`](https://togithub.com/TanStack/table/releases/tag/v8.10.0) [Compare Source](https://togithub.com/tanstack/table/compare/v8.9.11...v8.10.0) Version 8.10.0 - 9/17/2023, 12:58 AM #### Changes ##### Feat - Row Pinning ([#5074](https://togithub.com/tanstack/table/issues/5074)) ([`15a425a`](https://togithub.com/tanstack/table/commit/15a425af)) by [@KevinVandy](https://togithub.com/KevinVandy) #### Packages - [@tanstack/table-core](https://togithub.com/tanstack/table-core)[@8](https://togithub.com/8).10.0 - [@tanstack/react-table](https://togithub.com/tanstack/react-table)[@8](https://togithub.com/8).10.0 - [@tanstack/solid-table](https://togithub.com/tanstack/solid-table)[@8](https://togithub.com/8).10.0 - [@tanstack/vue-table](https://togithub.com/tanstack/vue-table)[@8](https://togithub.com/8).10.0 - [@tanstack/svelte-table](https://togithub.com/tanstack/svelte-table)[@8](https://togithub.com/8).10.0 ### [`v8.9.11`](https://togithub.com/TanStack/table/releases/tag/v8.9.11) [Compare Source](https://togithub.com/tanstack/table/compare/v8.9.10...v8.9.11) Version 8.9.11 - 9/15/2023, 4:49 PM #### Changes ##### Fix - limit deep keys even more ([`51214a8`](https://togithub.com/tanstack/table/commit/51214a88)) by Tanner Linsley ##### Chore - add more tests for row selection functions ([#5072](https://togithub.com/tanstack/table/issues/5072)) ([`31871e9`](https://togithub.com/tanstack/table/commit/31871e9d)) by [@KevinVandy](https://togithub.com/KevinVandy) #### Packages - [@tanstack/table-core](https://togithub.com/tanstack/table-core)[@8](https://togithub.com/8).9.11 - [@tanstack/react-table](https://togithub.com/tanstack/react-table)[@8](https://togithub.com/8).9.11 - [@tanstack/solid-table](https://togithub.com/tanstack/solid-table)[@8](https://togithub.com/8).9.11 - [@tanstack/vue-table](https://togithub.com/tanstack/vue-table)[@8](https://togithub.com/8).9.11 - [@tanstack/svelte-table](https://togithub.com/tanstack/svelte-table)[@8](https://togithub.com/8).9.11 ### [`v8.9.10`](https://togithub.com/TanStack/table/releases/tag/v8.9.10) [Compare Source](https://togithub.com/tanstack/table/compare/v8.9.9...v8.9.10) Version 8.9.10 - 9/15/2023, 12:09 AM #### Changes ##### Fix - getIsSomeRowsSelected should ignore unselectable rows (fix [#5060](https://togithub.com/tanstack/table/issues/5060)) ([#5061](https://togithub.com/tanstack/table/issues/5061)) ([`6c8fb5e`](https://togithub.com/tanstack/table/commit/6c8fb5e6)) by Joey Miller ##### Chore - rollback ts versions for older rollup compat ([#5071](https://togithub.com/tanstack/table/issues/5071)) ([`2f4b211`](https://togithub.com/tanstack/table/commit/2f4b2118)) by [@KevinVandy](https://togithub.com/KevinVandy) - upgrade faker and typescript ([#5070](https://togithub.com/tanstack/table/issues/5070)) ([`e7608ca`](https://togithub.com/tanstack/table/commit/e7608ca7)) by [@KevinVandy](https://togithub.com/KevinVandy) ##### Docs - Update header-group.md ([#4927](https://togithub.com/tanstack/table/issues/4927)) ([`e80fb3c`](https://togithub.com/tanstack/table/commit/e80fb3c3)) by [@mrlubos](https://togithub.com/mrlubos) #### Packages - [@tanstack/table-core](https://togithub.com/tanstack/table-core)[@8](https://togithub.com/8).9.10 - [@tanstack/react-table](https://togithub.com/tanstack/react-table)[@8](https://togithub.com/8).9.10 - [@tanstack/solid-table](https://togithub.com/tanstack/solid-table)[@8](https://togithub.com/8).9.10 - [@tanstack/vue-table](https://togithub.com/tanstack/vue-table)[@8](https://togithub.com/8).9.10 - [@tanstack/svelte-table](https://togithub.com/tanstack/svelte-table)[@8](https://togithub.com/8).9.10 ### [`v8.9.9`](https://togithub.com/tanstack/table/compare/605e13e6f05bd2e2493021b6f988ede05ccba498...5fe4bf4b6e99c95e2003821b37b4c6a8d5155719) [Compare Source](https://togithub.com/tanstack/table/compare/605e13e6f05bd2e2493021b6f988ede05ccba498...5fe4bf4b6e99c95e2003821b37b4c6a8d5155719)typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
### [`v6.7.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#670-2023-09-11) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.6.0...v6.7.0) ##### Bug Fixes - **eslint-plugin:** \[no-restricted-imports] disallow side effect imports when allowTypeImports is enabled ([#7560](https://togithub.com/typescript-eslint/typescript-eslint/issues/7560)) ([4908905](https://togithub.com/typescript-eslint/typescript-eslint/commit/4908905e4ee2b533504fcba0c671aa869668df25)) ##### Features - **eslint-plugin:** \[await-thenable] added suggestion fixer ([#7437](https://togithub.com/typescript-eslint/typescript-eslint/issues/7437)) ([b284370](https://togithub.com/typescript-eslint/typescript-eslint/commit/b284370e1e95493764d2806cd45975201e02f374)) You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.typescript-eslint/typescript-eslint (@typescript-eslint/parser)
### [`v6.7.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#670-2023-09-11) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.6.0...v6.7.0) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.pnpm/pnpm (pnpm)
### [`v8.7.6`](https://togithub.com/pnpm/pnpm/releases/tag/v8.7.6) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.7.5...v8.7.6) #### Patch Changes - Don't run the `prepublishOnly` scripts of git-hosted dependencies [#7026](https://togithub.com/pnpm/pnpm/issues/7026). - Fix a bug in which `use-node-version` or `node-version` isn't passed down to `checkEngine` when using pnpm workspace, resulting in an error [#6981](https://togithub.com/pnpm/pnpm/issues/6981). - Don't print out each deprecated subdependency separately with its deprecation message. Just print out a summary of all the deprecated subdependencies [#6707](https://togithub.com/pnpm/pnpm/issues/6707). - Fixed an ENOENT error that was sometimes happening during install with "hoisted" `node_modules` [#6756](https://togithub.com/pnpm/pnpm/issues/6756). #### Our Gold Sponsorssass/dart-sass (sass)
### [`v1.67.0`](https://togithub.com/sass/dart-sass/blob/HEAD/CHANGELOG.md#1670) [Compare Source](https://togithub.com/sass/dart-sass/compare/1.66.1...1.67.0) - All functions defined in CSS Values and Units 4 are now once again parsed as calculation objects: `round()`, `mod()`, `rem()`, `sin()`, `cos()`, `tan()`, `asin()`, `acos()`, `atan()`, `atan2()`, `pow()`, `sqrt()`, `hypot()`, `log()`, `exp()`, `abs()`, and `sign()`. Unlike in 1.65.0, function calls are *not* locked into being parsed as calculations or plain Sass functions at parse-time. This means that user-defined functions will take precedence over CSS calculations of the same name. Although the function names `calc()` and `clamp()` are still forbidden, users may continue to freely define functions whose names overlap with other CSS calculations (including `abs()`, `min()`, `max()`, and `round()` whose names overlap with global Sass functions). - **Breaking change**: As a consequence of the change in calculation parsing described above, calculation functions containing interpolation are now parsed more strictly than before. However, *almost* all interpolations that would have produced valid CSS will continue to work. The only exception is `#{$variable}%` which is not valid in Sass and is no longer valid in calculations. Instead of this, either use `$variable` directly and ensure it already has the `%` unit, or write `($variable * 1%)`. - **Potentially breaking bug fix**: The importer used to load a given file is no longer used to load absolute URLs that appear in that file. This was unintented behavior that contradicted the Sass specification. Absolute URLs will now correctly be loaded only from the global importer list. This applies to the modern JS API, the Dart API, and the embedded protocol. ##### Embedded Sass - Substantially improve the embedded compiler's performance when compiling many files or files that require many importer or function call round-trips with the embedded host.Configuration
📅 Schedule: Branch creation - "before 4am on sunday" (UTC), 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.