Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update dependencies (non-major) #907

Merged
merged 1 commit into from
Sep 18, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 17, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@aws-sdk/client-s3 (source) 3.409.0 -> 3.414.0 age adoption passing confidence
@aws-sdk/s3-request-presigner (source) 3.409.0 -> 3.414.0 age adoption passing confidence
@codemirror/view 6.18.0 -> 6.19.0 age adoption passing confidence
@playwright/test (source) 1.37.1 -> 1.38.0 age adoption passing confidence
@prisma/client (source) 5.2.0 -> 5.3.1 age adoption passing confidence
@tanstack/react-table 8.9.8 -> 8.10.0 age adoption passing confidence
@types/node (source) 18.17.15 -> 18.17.17 age adoption passing confidence
@typescript-eslint/eslint-plugin 6.6.0 -> 6.7.0 age adoption passing confidence
@typescript-eslint/parser 6.6.0 -> 6.7.0 age adoption passing confidence
pnpm (source) 8.7.4 -> 8.7.6 age adoption passing confidence
prisma (source) 5.2.0 -> 5.3.1 age adoption passing confidence
sass 1.66.1 -> 1.67.0 age adoption passing confidence

Release Notes

aws/aws-sdk-js-v3 (@​aws-sdk/client-s3)

v3.414.0

Compare Source

Features
  • region-config: add aws region runtime extension codegen (#​5157) (b9d59e8)

v3.413.0

Note: Version bump only for package @​aws-sdk/client-s3

v3.412.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-s3

v3.410.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-s3

aws/aws-sdk-js-v3 (@​aws-sdk/s3-request-presigner)

v3.414.0

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.413.0

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.412.0

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.410.0

Note: Version bump only for package @​aws-sdk/s3-request-presigner

codemirror/view (@​codemirror/view)

v6.19.0

Compare Source

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

Compare Source

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

Compare Source

UI Mode Updates

Playwright UI Mode

  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:

- 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:

// 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
prisma/prisma (@​prisma/client)

v5.3.1

Compare Source

Today, we are issuing the 5.3.1 patch release.

Fix in Prisma Client

v5.3.0

Compare Source

🌟 Help us spread the word about Prisma by starring the repo or tweeting 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:
// 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.
VS Code extension 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
Prisma Client
Language tools (e.g. VS Code)

Credits

Huge thanks to @​alencardc, @​Oreilles, @​christianledgard, @​skyzh, @​alula, @​michaelpoellath, @​RobertCraigie, @​stephenwade for helping!

tanstack/table (@​tanstack/react-table)

v8.10.0

Compare Source

Version 8.10.0 - 9/17/2023, 12:58 AM

Changes

Feat

Packages

v8.9.11

Compare Source

Version 8.9.11 - 9/15/2023, 4:49 PM

Changes

Fix
  • limit deep keys even more (51214a8) by Tanner Linsley
Chore

Packages

v8.9.10

Compare Source

Version 8.9.10 - 9/15/2023, 12:09 AM

Changes

Fix
Chore
Docs

Packages

v8.9.9

Compare Source

typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v6.7.0

Compare Source

Bug Fixes
  • eslint-plugin: [no-restricted-imports] disallow side effect imports when allowTypeImports is enabled (#​7560) (4908905)
Features
  • eslint-plugin: [await-thenable] added suggestion fixer (#​7437) (b284370)

You can read about our versioning strategy and releases on our website.

typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v6.7.0

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

You can read about our versioning strategy and releases on our website.

pnpm/pnpm (pnpm)

v8.7.6

Compare Source

Patch Changes

  • Don't run the prepublishOnly scripts of git-hosted dependencies #​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.
  • Don't print out each deprecated subdependency separately with its deprecation message. Just print out a summary of all the deprecated subdependencies #​6707.
  • Fixed an ENOENT error that was sometimes happening during install with "hoisted" node_modules #​6756.

Our Gold Sponsors

Our Silver Sponsors

v8.7.5

Compare Source

Patch Changes
  • Improve performance of installation by using a worker for creating the symlinks inside node_modules/.pnpm #​7069.
  • Tarballs that have hard links are now unpacked successfully. This fixes a regression introduced in v8.7.0, which was shipped with our new in-house tarball parser #​7062.
Our Gold Sponsors
Our Silver Sponsors
sass/dart-sass (sass)

v1.67.0

Compare Source

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


  • If you want to rebase/retry this PR, check this box

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

@vercel
Copy link

vercel bot commented Sep 17, 2023

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
Copy link

github-actions bot commented Sep 17, 2023

Coverage Report

Status Category Percentage Covered / Total
🔵 Lines 100% 147 / 147
🔵 Statements 100% 147 / 147
🔵 Functions 100% 4 / 4
🔵 Branches 100% 17 / 17
File CoverageNo changed files found.
Generated in workflow #182

@leomotors leomotors merged commit 0b080b3 into main Sep 18, 2023
@leomotors leomotors deleted the renovate/dependencies-(non-major) branch September 18, 2023 01:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant